Network performance monitoring

Maintain responsive and performant networks no matter how widely distributed your resources are.

The basics of network performance monitoring

Three network performance monitoring pillars separate the unmonitored from the monitored network — and if you feed this data into a centralized time series platform you will be able to enable holistic network performance monitoring.

Networks play a fundamental role in the adoption and growth of Internet applications. Penetrating enterprises, homes, factories, and even cities, networks sustain modern society. While assuring responsive and performant networks in today’s hybrid, distributed and containerized application environments occurs behind the scenes in intangible clouds and diagrams abstractions, network glitches are more visible and unforgiving than ever.

The basics of network performance monitoring

Network availability, responsiveness, and bandwidth consumption are the three pillars that separate unmonitored from the monitored networks — and if you feed this data into a centralized time series platform you will be able to have a holistic view of your network performance monitoring.

Network availability

Network availability refers to host reachability. If the network is unavailable, there could be something related to the endpoint health or network path (such as a load balancer’s sessions limit or expired SSL) preventing traffic from reaching the host.

Network responsiveness

Network responsiveness is the combination of latency and packet loss. Latency refers to the time it takes for traffic to cross the network to a target, and packet loss determines the error rate experienced. Latency and packet loss render the network suitable for all or some more sensitive applications. For instance, high latency will completely undermine unified communications (voice & video) services.

Network bandwidth consumption

Network bandwidth consumption tracks metrics from the network interface providing important information about bandwidth load at the interface, which can be used to set up alerts before the interface is completely saturated. Adding to the network interface metrics data from network traffic analysis appliances allows for identification of bandwidth consumption struggles, providing precious insights about sessions and IPs/protocol/port troublemakers that are causing saturation, as well as identifying resource misuse and potential Denial of Service (DoS) attacks.

The functional architecture of the InfluxData network monitoring platform

the architecture of the InfluxData network monitoring platform

Telegraf is the collection agent with 200+ plugins and a vast client library, that can source metrics directly from the system it’s running on, pull metrics from third-party APIs, listen for metrics via streaming consumer services, and support monitoring protocols such as ICMP/Ping, SNMP, NETFlow and SFlow, as well as gathering metrics and logs with Syslog.


InfluxDB is the database and storage engine purpose-built to handle time series data. A perfect metric store for multiple data sources to help you avoid a siloed approach. In InfluxDB 1.0, Chronograf (visualization tool with pre-canned dashboards with the standard baseline for network monitoring) and Kapacitor (rules engine for processing, monitoring, and alerting) are separate components of the TICK Stack. InfluxDB 2.0 comes with Chronograf and Kapacitor built-in.

Find more information about network monitoring plugins:

Coupa SoftwareInfluxDB Cloud is providing improved visibility across areas where we previously couldn’t see, allowing us to proactively identify and fix issues before customers find them.

Sanket Niak
VP of Cloud Operations and Security • Coupa

Case study


NewVoiceMedia, a UK-based cloud service company, chose InfluxData to provide 99.999% uptime monitoring of its global SaaS because InfluxData could meet and exceed its business and technical requirements. Grafana is used for all its graphing capabilities.

Case study


In just 4 weeks, Coupa (a cloud platform for business spend), was able to go beyond building a proof-of-concept with InfluxData, and was able to create a working prototype that was kept simple and iterated upon often: It used Telegraf to collect data, a single InfluxDB node to store data, Grafana to visualize data, and Kapacitor to analyze data.

Case study


Using InfluxDB, ntopng is open to “big data” systems that can scale with data in volume and speed. It is able to export monitoring information in JSON format towards various systems including Elasticsearch/Logstash and ZMQ. ntopng is also able to collect, self-produce (from packets), and export monitoring information by normalizing it in JSON format.

Learn more about Network Monitoring
How to Use Google Core IoT with InfluxData

As more and more IoT deployments look to leverage the power of cloud-based solutions, we here at InfluxData have been working closely with Cloud Service Providers to make sure that InfluxDB continues to be the go-to Time Series Database for IoT. Google’s Core IoT...

Learning Go with the InfluxDB Go Library

I’m not a Golang developer. Let’s just get that out of the way up front. I’ve developed a few things in Go, but a Go developer I’m not. I sort of need to be, but it hasn’t been essential. I decided that it was really time to take the plunge and get serious about Go....

Contact Sales