Docs » Configure application receivers » Configure application receivers for networks » Network interface I/O

Network interface I/O 🔗

Description 🔗

The Splunk Distribution of OpenTelemetry Collector provides this integration as the net-io monitor via the Smart Agent Receiver.

This monitor reports I/O metrics about network interfaces. See signalfx-agent/pkg/monitors/netio/ for the monitor source.

Installation 🔗

This monitor is available in the SignalFx Smart Agent Receiver, which is part of the Splunk Distribution of OpenTelemetry Collector.

To install this integration:

  1. Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform.

  2. Configure the monitor, as described in the next section.

Configuration 🔗

The Splunk Distribution of OpenTelemetry Collector allows embedding a Smart Agent monitor configuration in an associated Smart Agent Receiver instance.

Note: Providing a net-io monitor entry in your Smart Agent or Collector configuration is required for its use. Use the appropriate form for your agent type.

Smart Agent 🔗

To activate this monitor in the Smart Agent, add the following to your agent configuration:

monitors:  # All monitor config goes under this key
  - type: net-io
    ...  # Additional config

See Smart Agent example configuration for an autogenerated example of a YAML configuration file, with default values where applicable.

Splunk Distribution of OpenTelemetry Collector 🔗

If you are using the Splunk Distribution of OpenTelemetry Collector and want to collect network interface I/O and TCP connection metrics, use the Host Metrics Receiver.

Configuration settings 🔗

The following table shows the configuration options for the net-io monitor:

Option Required Type Description
interfaces no list of strings The network interfaces to send metrics about. This is an overridable set. (default: [* !/^lo\d*$/ !/^docker.*/ !/^t(un|ap)\d*$/ !/^veth.*$/ !/^Loopback*/])

On Linux hosts, this monitor relies on the /proc filesystem. If the underlying host’s /proc file system is mounted somewhere other than /proc, specify the path using the top-level configuration procPath, as shown in the following example:

procPath: /proc
monitors:
 - type: net-io

Metrics 🔗

These are the metrics available for this integration.