There is nothing technically wrong with the current setting. Warm buckets did not roll to cold because none of the criteria for rolling buckets were met. Reaching the minimum disk space is not a cr...
See more...
There is nothing technically wrong with the current setting. Warm buckets did not roll to cold because none of the criteria for rolling buckets were met. Reaching the minimum disk space is not a criterium. Buckets roll either because the index is too full, the bucket(s) are too old, or the maximum number of warm buckets has been reached.
We are using Splunk Enterprise Version: 9.3.1 and we need it for Classic Dashboard What I managed to put together is this : <html>
<style type="text/css">
table tr:nth-...
See more...
We are using Splunk Enterprise Version: 9.3.1 and we need it for Classic Dashboard What I managed to put together is this : <html>
<style type="text/css">
table tr:nth-child(odd) td{color: red;
}
table tr:nth-child(even) td{color: green;
}
</style>
</html>
It looks like this : What I actually need is to Select rows Containing INFO / ERROR / WARNING and color them RED , BLUE , YELLOW
Ok thanks, i get this part, i'll try to rework the indexes.conf. But what i still don't get, and i really would like to know (it's quite important for me to know what was wrong before changing anythi...
See more...
Ok thanks, i get this part, i'll try to rework the indexes.conf. But what i still don't get, and i really would like to know (it's quite important for me to know what was wrong before changing anything) is why it didn't work in the first place ? From what i read in the doc it should have work with a simple conf like this no ? Furthermore, using a Volume and maxVolumeDataSizeMB will help me monitor the global size of all indexes on my volume right ? But i need each indexes to possibly have a specific maxTotalDataSIzeMB and abide by it. If it's not possible or limited (because of whatever reason) feel free to tell me. Thanks again !
Assuming your csv is called numbers.csv and the field if called number, try something like this index=* [| inputlookup numbers.csv | rename number as search | table search]
We are setting colours of charts from our company standards but this seems to have broken since friday, we think it may be browser or html updates rather than splunk Example code we use is
/* CH...
See more...
We are setting colours of charts from our company standards but this seems to have broken since friday, we think it may be browser or html updates rather than splunk Example code we use is
/* CHART COLOURS FOR LEGEND */
.highcharts-legend .highcharts-series-0 .highcharts-point{
fill:#28a197;
}
.highcharts-legend .highcharts-series-1 .highcharts-point{
fill:#f47738;
}
.highcharts-legend .highcharts-series-2 .highcharts-point{
fill:#6f72af;
}
/*BAR CHART FILL AREA */
.highcharts-series-0 .highcharts-tracker-area {
fill:#28a197;
stroke:#28a197;}
.highcharts-series-1 .highcharts-tracker-area {
fill:#f47738;
stroke: #f47738;}
.highcharts-series-2 .highcharts-tracker-area {
fill:#6f72af;
stroke: #6f72af;}
/* PIE CHART COLOURS */
.highcharts-color-0 {
fill: #28a197 ;
}
.highcharts-color-1 {
fill: #f47738;
}
.highcharts-color-2 {
fill: #6f72af;
}
Bar charts broke first and we found if we replaced .highcharts-tracker-area with .highcharts-point then it fixed the bars but then allowed pie charts to be only one colour
Whether it takes long to search it depends on your data. If these are really long and fairly unique terms, they can be (relatively) quickly searchable provided that you're looking strictly for those ...
See more...
Whether it takes long to search it depends on your data. If these are really long and fairly unique terms, they can be (relatively) quickly searchable provided that you're looking strictly for those terms, not some wildcarded variations (especially with wildcard not at the end of the search term).
It's not about a field but more about the general layout and variability of data in your DB. Splunk works differently - once you ingest an event, it's immutable whereas the contents of a particular r...
See more...
It's not about a field but more about the general layout and variability of data in your DB. Splunk works differently - once you ingest an event, it's immutable whereas the contents of a particular row in DB can change. So regardless of how you decide that one row of your results has already been ingested, it won't be ingested again even if some "secondary" fields change their values. I don't know your data, I don't know what it represents. If you reconfigure your DB data onboarding process to ingest both states of your DB record (or whatever result set you're getting), you'll have in Splunk two separate partly duplicated events and will have to handle it somehow in search-time.
Okay. Could you check/verify if you use the Distributed Monitoring Console and if the affected HFs are configured as Indexer under Settings --> Monitoring Console --> Settings --> General Setup? Th...
See more...
Okay. Could you check/verify if you use the Distributed Monitoring Console and if the affected HFs are configured as Indexer under Settings --> Monitoring Console --> Settings --> General Setup? That could be the reason why the HeavyForwarder are configured as distributed search peers to monitor them in the DMC. So if the license manager on the same instance as the DMC is check the config files for the affected HFs and may remove them.
I have a heavy's without master_uri and Manager_uri. They are luckely working okay besides the error. In etc/licenses is only download-trial folder. No forwarder.license
Hi @Crotyo , you should put the csv file in a lookup (called e.g. "my_lookup.csv", containing at least one field (e.g. "my_field") and then run a search like the following: index=* [ | inputlookup ...
See more...
Hi @Crotyo , you should put the csv file in a lookup (called e.g. "my_lookup.csv", containing at least one field (e.g. "my_field") and then run a search like the following: index=* [ | inputlookup my_lookup.csv | rename my_field AS query | fields query ]
| ... in this way you perform a search in full text search mode on all the events. Ciao. Giuseppe
I have a csv file like this that contain more than 100 numbers 11111111 22222222 33333333 I want to search for events that contain these number. I can use index=* "11111111" OR "22222222" ...
See more...
I have a csv file like this that contain more than 100 numbers 11111111 22222222 33333333 I want to search for events that contain these number. I can use index=* "11111111" OR "22222222" but it take way to long. Is there a faster way? these number does not have a seperate fields or am i searching in any fields. im just searching for any event log that contain these number. Can anyone help? Thanks.
Hi Uma
You just have to create a metric per Token and use a query like this
SELECT toInt(expirationDateTime- eventTimestamp) AS "Seconds" which will give you the difference in seconds between the...
See more...
Hi Uma
You just have to create a metric per Token and use a query like this
SELECT toInt(expirationDateTime- eventTimestamp) AS "Seconds" which will give you the difference in seconds between the dates, you can then further multiply the seconds to get minutes/hours or days if you want to rather use that.
This will give you the metric to tell you how much seconds/minutes/hours/days to expiry and you can then alert on it
Ciao
To accept the license during the start, execute: opt/splunkforwarder/splunk start --accept-license --answer-yes and before you start the forwarder service I suggest to create a user-seed.conf to se...
See more...
To accept the license during the start, execute: opt/splunkforwarder/splunk start --accept-license --answer-yes and before you start the forwarder service I suggest to create a user-seed.conf to set the admin password in clear text on the CLI. user-seed.conf must be stored in /opt/splunkforwarder/etc/system/local/ [user_info]
USERNAME = admin PASSWORD = YourPassword another method is to hash the password and add the hash to the user-seed.conf. It is described in the following doc Create secure administrator credentials - Splunk Documentation
Thanks for the response Paul.. I removed the master_uri. I can understand why, it is now manager_uri see below: /opt/splunk/etc/system/local/server.conf [license] /opt/splunk/etc/system/local/serv...
See more...
Thanks for the response Paul.. I removed the master_uri. I can understand why, it is now manager_uri see below: /opt/splunk/etc/system/local/server.conf [license] /opt/splunk/etc/system/local/server.conf active_group = Forwarder /opt/splunk/etc/system/default/server.conf connection_timeout = 30 /opt/splunk/etc/system/default/server.conf manager_uri = self /opt/splunk/etc/system/default/server.conf receive_timeout = 30 /opt/splunk/etc/system/default/server.conf report_interval = 1m /opt/splunk/etc/system/default/server.conf send_timeout = 30 /opt/splunk/etc/system/default/server.conf squash_threshold = 2000 /opt/splunk/etc/system/default/server.conf strict_pool_quota = true I did something else, and that is remove the heavy's from the distributed search peers. Why they where there i don't know. It resolved one thing, the warning about disabling the peer... The only thing remaining is the duplicate license hash (ffffff...) in the _internal index. I can understand the hash itself. Every forwaredr with this license has this hash. What i don't understand is why this warnimng. And it is only the warning for the heavy's which were in the distributed serach peers. Not the one's which were not in that list. It seems something remained someweher and keeps looking to the license on these heavy's and keeps reporting it is the same license... Any idea?
Hi @PickleRick, If I replace the TASKID column with UPDATED column to rising column method, will it make a difference? FYI : I also increased the checkpoint value from 1 to 2 and even after the...
See more...
Hi @PickleRick, If I replace the TASKID column with UPDATED column to rising column method, will it make a difference? FYI : I also increased the checkpoint value from 1 to 2 and even after the second time STATUS change is RELEASED to FINISHED, that row is not ingested in splunk.