Splunk Search

Assessing an Avg on an seen IP

itsmevic
Communicator

Hello,

I'd like to run an average over the course of May 16, 2020 (24-hours), on a particular IP address.  I'd like to see an event count on this IP with an average overlay over the course of a 24-hour timespan on the indicated date above.

Heres my base query:

index=* "IP Address"
|timechart count by src
|sort -count

Suggestions are greatly welcomed and very much appreciated.
0 Karma

to4kawa
Ultra Champion
index=your_index src="X.X.X.X"
|timechart span=1h count 
|eventstats avg(count) as hourly_avg

an average over the course of May 16, 2020 (24-hours)

I'm not sure because the units are not indicated.
People all love average, but most of the time the formula isn't obvious.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

You have your own suggestion right there. Does it not work as expected? If not. what are you getting compared to what you want?
Be aware that searching for an IP address can be a problem because of the way Splunk treats the dots in the address. You may need to use the TERM operator.

---
If this reply helps you, Karma would be appreciated.
0 Karma

itsmevic
Communicator

Unfortunately, the TERM operator doesn't work due to the IP's [.] dot's. I tried searching on TERM(xx.xx.xxx.xxx) and the search choked.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...