Linux Network Interface Monitoring
Network interface monitoring in Linux involves tracking and managing individual network interfaces within Linux-based systems. By continuously monitoring network interfaces on Linux systems, administrators can track bandwidth usage, optimize resource allocation, detect network errors or congestions, and troubleshoot connectivity issues that may impact system performance and reliability.
Monitoring network interfaces in IT-Conductor enables real-time visibility into network interface status, errors, throughput, remote host ping statistics, etc. It allows the identification of networking issues without full-fledged network monitoring infrastructure.
To view the Linux network interface metrics, locate the Network Interfaces node in the Linux Systems grid.
Note: Only interface status, IP addresses, and other details are initially pulled.
Configure Extended Network Interface in IT-Conductor
If required, IT-Conductor can utilize the ifstat
command to collect other network interface metrics. To enable this feature, follow the instructions below.
Click Configuration in the Network Interfaces grid.
Note: The newly collected metrics will appear in the service grid within 5-15 minutes.
Verify if the newly collected metrics are showing properly in the Network Interfaces grid.
Network Interfaces Extended Metrics
State - refers to the current operational state of the network interface.
RX Data - refers to the amount of data received (in bytes) by the network interface.
RX Dropped - refers to the number of incoming packets dropped by the network interface due to issues like buffer overflows or congestion.
TX Data - refers to the amount of data transmitted (in bytes) by the network interface.
TX Dropped - refers to the number of outgoing packets dropped by the network interface, typically due to congestion or other network issues.
TX Errors - represents the number of transmission errors encountered by the network interface, which could include issues like collisions or failed transmissions.
Note: The thresholds can be set up for all monitors. See Creating Threshold Overrides for more information.
Configure Remote Host Ping Monitoring in IT-Conductor
Host ping is deactivated by default.
Activate Host Ping
To activate host ping, follow the instructions below.
Click Properties in the Linux System grid.
Check the Network Ping Monitoring option, and then click Save.
Verify if the Host Ping node shows in the Linux System grid.
Configure Individual Host Ping
To set up individual host ping, follow the instructions below.
Click Configuration in the Host Ping grid.
Fill out all the necessary information in the Create Host Ping Retriever configuration page. Once completed, click Finish to add the system.
Note:
Specify a proper name and host(s). Multiple hosts should be separated by spaces.
You can override the default Linux ping command parameters: Interval, Packets, & Timeout.
Verify if the newly collected metrics are showing properly in the Host Ping grid.
Host Ping Key Metrics
Packet Loss - refers to the percentage of packets that fail to reach their destination over a network interface. It aggregates all ping result records and alerts on each host that has a loss value above the threshold.
Response Time - refers to the time it takes for a packet to travel from its source to its destination and back.
Verify the additional Response Time monitor in the Host Ping grid.
View Historical Ping Results
To view historical ping results, navigate to the Packet Loss explorer and click on any data point (green circle) on the chart line to display the ping result records for the interval selected.
Note: The same approach can be applied to Response Time monitors.
View Historical Response Time
To view historical response time, navigate to the specific host's Response Time explorer and click on any data point (green circle) on the chart line to display the response time records for the interval selected.
Last updated