All Posts

Find Answers
Ask questions. Get answers. Find technical product solutions from passionate members of the Splunk community.

All Posts

I want to know how much CPU is utilized in our environment along with the trendline @ITWhisperer 
How are you getting your current results - what's your existing SPL?
Have you tried setting TIME_FORMAT in props.conf, e.g. TIME_FORMAT = %s%9Q I suspect you won't get nanoseconds, but you should get microseconds, for example this can get microseconds | makeresults... See more...
Have you tried setting TIME_FORMAT in props.conf, e.g. TIME_FORMAT = %s%9Q I suspect you won't get nanoseconds, but you should get microseconds, for example this can get microseconds | makeresults | eval tf="1707613171105412540" | eval t=strptime(tf, "%s%9Q")
That's fine, but it still doesn't say which servers go in the left panel and which go in the right - how do you decide that logic - anyway, my previous post gives you an example to work with, I hope ... See more...
That's fine, but it still doesn't say which servers go in the left panel and which go in the right - how do you decide that logic - anyway, my previous post gives you an example to work with, I hope you can give that a go and see if it can get you where you're trying to get to.
So I have a schedule search running on DS to summery index which pulls all the info from two DS. Index=summery source=sc. which has the serveclass, forwarder, deplyment server, deployementappname inf... See more...
So I have a schedule search running on DS to summery index which pulls all the info from two DS. Index=summery source=sc. which has the serveclass, forwarder, deplyment server, deployementappname info.   
Yes, I realised as soon as I posted, so did the isnotnull test
The problem with this is that you will get the same count for all time periods whether or not the node was "present" in that time period. The original (second) search uses dc(node) which will only co... See more...
The problem with this is that you will get the same count for all time periods whether or not the node was "present" in that time period. The original (second) search uses dc(node) which will only count the unique instances of node present in each time period.
It is not clear what your events look like but assuming each event has an ERROR_MESSAGE field and you want to count by that message and work out the percentage of the total this represents, you could... See more...
It is not clear what your events look like but assuming each event has an ERROR_MESSAGE field and you want to count by that message and work out the percentage of the total this represents, you could do something like this | stats count by ERROR_MESSAGE | eventstats sum(count) as total | eval count=100*count/total
There's always a way to get where you want to go with Splunk, The issue you have is that timechart with a split by does not end up with a field called node anymore, as the value of node is now the c... See more...
There's always a way to get where you want to go with Splunk, The issue you have is that timechart with a split by does not end up with a field called node anymore, as the value of node is now the column name. You could use stats by time and other mangling of data, but you'd have to handle missing buckets of time in the average, so a simple solution is to effectively count the columns like this   | timechart avg(stat1) by node | eval _nodes=0 | foreach * [ eval _nodes=_nodes + if(isnotnull('<<FIELD>>'), 1, 0) ] | rename _nodes as nodes   Note the underscore in front of the field name - this prevents Splunk from including this in the * matching for foreach. It will create one more column called nodes with the count of nodes.
Try something like this | timechart span=1h avg(stat1) by node | untable _time node avg | appendpipe [| stats count as avg by _time | eval node="Nodes"] | xyseries _time node avg
You haven't explained a fundamental part of the problem - how do you know which servers go in to US and which servers go into UK (or EAST and WEST as in your example). You need to know how you can t... See more...
You haven't explained a fundamental part of the problem - how do you know which servers go in to US and which servers go into UK (or EAST and WEST as in your example). You need to know how you can tell if server 1 belongs to panel 1 or panel 2. Then you simply need to have a base search that splits up the selected servers according to their region, e.g. | makeresults | eval servers=split($server|s$, ",") | eval region=<<DEFINE YOUR LOGIC HERE TO CREATE REGION BASED ON HOST>>> | stats values(server) as server by region | eval server=mvjoin(server, ",") | transpose 0 header_field=region and then you have a <done> clause where you set the tokens for each panel accordingly <done> <set token="region_1">$result.region_1$</set> <set token="region_2">$result.region_2$</set> </done> and you then use the region_1 and 2 tokens in your panels instead of $server$
Colours are assigned to series i.e. all bars from the same series are in the same colour. This is because of the way they are drawn in the chart viz i.e. they are drawn as a single shape for the whol... See more...
Colours are assigned to series i.e. all bars from the same series are in the same colour. This is because of the way they are drawn in the chart viz i.e. they are drawn as a single shape for the whole series, not individual bars. If you want them to have different colours, they need to be different series. Think of the table of data, all data points in the same column of the table will have the same colour in the chart.
Not sure if this is feasible. Basically I would like a chart that shows the average of a statistic for different nodes and distinct count of different nodes. so the 2 searches would be something like... See more...
Not sure if this is feasible. Basically I would like a chart that shows the average of a statistic for different nodes and distinct count of different nodes. so the 2 searches would be something like: 1. index=xxx sourcetype=yyy |timechart avg(stat1) by node 2. index=xxx sourcetype=yyy|timechart dc(node) Both searches would showup on the same timechart panel for the same period with the same time span. Sorry if this is unclear, happy to clarify. I tried eventstats, append, appendcols, and join, but they do not seem to work for this. Could be I'm misusing them though.
The original query: host="MEIPC" source="WinEventLog:Application" OR source="WinEventLog:Security" OR source="WinEventLog:System" |chart count by source A could be solution I could not get to wor... See more...
The original query: host="MEIPC" source="WinEventLog:Application" OR source="WinEventLog:Security" OR source="WinEventLog:System" |chart count by source A could be solution I could not get to work: | top limit=10 class showperc=f countfield="source" | reverse | transpose header_field="Class" column_name="Class" | search class="source" So I tried searching all over to change the color of the bars of each of 3 sources I gathered data from. I put it in the dashboard and I noticed that it groups it all under an encompassing source, without an individual option for each source. This is labeled under the X axis. However, when I try to change the color of the bars, only changing the color of count which is the Y axis changes the color of the bars. This confuses me because I would think that I can simply change the color options in the menus of dashboard for each individual  X axis source but instead its the Y axis count that changes the color of the bars, and there is no option to change the coloration to the X axis source. What also confuses me, is when I look at statistics, there are 3 sources to gather the data from. Please leave a comment if you have the time, thank you so much Splunk Community!
I don't want to get too specific, because it may work different for different environments, but it they keys were: mount.cifs to mount the windows drive on athe destination linux machine rsync -avh... See more...
I don't want to get too specific, because it may work different for different environments, but it they keys were: mount.cifs to mount the windows drive on athe destination linux machine rsync -avhipP copied from the windows drive to the linux drive and adjusted from a windows file structure to a linux file structure.
I got a visualization that counts the total amount of errors using a lookup. Instead of the actual number of events I'd like to get a percentage of specifically errors. Image attached for reference  ... See more...
I got a visualization that counts the total amount of errors using a lookup. Instead of the actual number of events I'd like to get a percentage of specifically errors. Image attached for reference      | inputlookup fm4143_3d.csv | stats count(ERROR_MESSAGE) ```| appendpipe [| stats count as message | eval message=if(message==0,"", " ")] | fields - message ```
I did not find anything weird about the interface stats. Similar problem occurs in all Linux nodes, but differs in period/delay. There is btool output configuration     
I am getting blank value   index="webmethods_prd" host="USPGH-WMA2AISP*" source="/apps/WebMethods/IntegrationServer/instances/default/logs/ExternalPAEU.log" ("success" OR "fail*")| eval stat... See more...
I am getting blank value   index="webmethods_prd" host="USPGH-WMA2AISP*" source="/apps/WebMethods/IntegrationServer/instances/default/logs/ExternalPAEU.log" ("success" OR "fail*")| eval status = if(searchmatch("success"), "Success", "Error")|stats count by source,status| xyseries source status count| eval source=case( source="*PAEU.log", "Canada Pricing Call")
I am getting blank value index="webmethods_prd" host="USPGH-WMA2AISP*" source="/apps/WebMethods/IntegrationServer/instances/default/logs/ExternalPAEU.log" ("success" OR "fail*")| eval status =... See more...
I am getting blank value index="webmethods_prd" host="USPGH-WMA2AISP*" source="/apps/WebMethods/IntegrationServer/instances/default/logs/ExternalPAEU.log" ("success" OR "fail*")| eval status = if(searchmatch("success"), "Success", "Error")|stats count by source,status| xyseries source status count| eval source=case( source="*PACA.log", "Canada Pricing Call")
Search level extraction : I am thinking instead of json extraction I think it could be easy to add index extraction as json so that each event will treat as json message and the remaining few lines w... See more...
Search level extraction : I am thinking instead of json extraction I think it could be easy to add index extraction as json so that each event will treat as json message and the remaining few lines we can do extraction at the search level. let me know your thoughts ? @KendallW