Splunk Search

windows perfmon network utilization

ggfsplunk
Engager

ggfsplunk_0-1613271152571.png

I'm trying to figure out to calculate the network utilization on this server using the eval and stats and I'm having problem figuring out the correct search and expression, can you help me.

 

index=* sourcetype="Perfmon:Network Interface" source="Perfmon:Network Interface" counter=*
| eval bytes_out = "Bytes Sent/sec", bytes_in = "Bytes Received/sec"
| eval Bandwidth = bytes_out + bytes_in
| timechart count by Bandwidth limit=10

 

I need to convert the bytes in mbps, as well, I would really appreciate some help here, Thank you in advance.

Labels (2)
0 Karma
1 Solution

ggfsplunk
Engager

Thank you so much, search works, just slight modification on last pipe | timechart avg(bandwidth_mpbs)...

View solution in original post

0 Karma

snehalharshe16
Observer

Hey

Run PerfMon from any command line (or type "Performance Monitor" in the Start menu), right-click on "Performance", select "Connect to another computer", and enter the IP address of the Nano Server computer you want to monitor. 

0 Karma

ggfsplunk
Engager

Thank you so much, search works, just slight modification on last pipe | timechart avg(bandwidth_mpbs)...

0 Karma

lydiapal_splunk
Splunk Employee
Splunk Employee

Happy to help! Sorry for the typo.. 😅

0 Karma

lydiapal_splunk
Splunk Employee
Splunk Employee

Hi!

Something like this should help you:

index=* sourcetype="Perfmon:Network Interface" source="Perfmon:Network Interface" counter=*
| eval bytes_out=if(counter="Bytes Sent/sec",Value,0), bytes_in=if(counter="Bytes Received/sec",Value,0)
| eval bandwidth_mbps=(bytes_out+bytes_in)/1024/1024
| timechart avg(bandwidth)

Please replace index=* with your index name, as it is bad practise to use index=*.

I'd strongly suggest doing the free Splunk Fundamentals 1 course, it will help you understand basic SPL better.

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to February Tech Talks, Office Hours, and Webinars!

💌 Keep the new year’s momentum going with our February lineup of Community Office Hours, Tech Talks, ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Incident Response: Reduce Incident Recurrence with Automated Ticket Creation

Culture extends beyond work experience and coffee roast preferences on software engineering teams. Team ...