Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
check_int_traffic - Interface traffic for Linux, Solaris, Windows and NetApp filer
Current Version
1.2
Last Release Date
2012-10-10
Compatible With
- Nagios 3.x
Owner
License
Other
Hits
64141
Files:
| File | Description |
|---|---|
| check_int_traffic.1.2 | The plugin itself |
| check_int_traffic.php | The pnp4nagios template |
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
By Martin Fuerstenau
This plugin check the network traffic for each network interface for Linux, Solaris, Windows and NetApp filer. It is not necessary to submit the operating system because it is automatically detected.
On Windows systems all virtual interfaces (wlan, leightweight filter, ISATAP etc.) are filtered out. But if it is needed it is easy to enable it because the filter are some simple if statements which can be commented out.
With the optional -d the plugin will cause an alam if an interface is down.
Performance data is generated. To collect it with pnp4nagios a template is enclosed.
On Windows systems all virtual interfaces (wlan, leightweight filter, ISATAP etc.) are filtered out. But if it is needed it is easy to enable it because the filter are some simple if statements which can be commented out.
With the optional -d the plugin will cause an alam if an interface is down.
Performance data is generated. To collect it with pnp4nagios a template is enclosed.
Reviews (4)
byaiiqbal88, November 25, 2019
@spicysomtam can you please upload your script as well in your listings? also have you done it with snmp3
bylmiltchev, November 19, 2015
@spicysomtam
Make your own post, and upload the script you updated. Provide a URL link to the "original" plugin. Thanks!
Make your own post, and upload the script you updated. Provide a URL link to the "original" plugin. Thanks!
byFractalSystems, November 18, 2015
@spicysomtam can you please share your updates direct to me? They sound exactly what I need as well.
byspicysomtam, September 1, 2015
2 of 2 people found this review helpful
This plugin almost did what I wanted, so I added some enhancements to make it perfect for our needs:
Added --notraffic (-n) and --match (-m) args: So we can skip no traffic interfaces and pattern match on the interface name using a regex. On linux hosts you can have alot of interfaces, and we are not interested in ones not used (eg have no traffic). The notraffic arg also prevents supurious alerts when not in use interfaces are down and -b is specified. Also sorted the output on interface name order; rather than being jumbled up. This makes bond interfaces display before eth interfaces; it just makes much more sense as a bond interface is typically made up of several eth interfaces. So we would see: OK. bond0:up eth0:up eth1:up eth2:up eth3:up eth4:up eth5:up. The pattern match allows you to only include interfaces that match the pattern. Eg (bond|eth|em|eno).
Thanks for writing the script, and with some tweaks I was able to do everything we needed.
Where can I upload the script I updated?
Added --notraffic (-n) and --match (-m) args: So we can skip no traffic interfaces and pattern match on the interface name using a regex. On linux hosts you can have alot of interfaces, and we are not interested in ones not used (eg have no traffic). The notraffic arg also prevents supurious alerts when not in use interfaces are down and -b is specified. Also sorted the output on interface name order; rather than being jumbled up. This makes bond interfaces display before eth interfaces; it just makes much more sense as a bond interface is typically made up of several eth interfaces. So we would see: OK. bond0:up eth0:up eth1:up eth2:up eth3:up eth4:up eth5:up. The pattern match allows you to only include interfaces that match the pattern. Eg (bond|eth|em|eno).
Thanks for writing the script, and with some tweaks I was able to do everything we needed.
Where can I upload the script I updated?
