NetMeter icon

NetMeter

NetMeter

Plugin: go.d.plugin Module: prometheus

Overview

Monitor NetMeter network traffic metrics for efficient network management and performance.

Metrics are gathered by periodically sending HTTP requests to NetMeter Exporter.

This collector is supported on all platforms.

This collector supports collecting metrics from multiple instances of this integration, including remote instances.

Default Behavior

Auto-Detection

By default, it detects instances running on the local host by trying to connect to known ports that are allocated to exporters. The full list of endpoints is available in the collector’s configuration file.

Limits

The default configuration for this integration does not impose any limits on data collection.

Performance Impact

The default configuration for this integration is not expected to impose a significant performance impact on the system.

Setup

Prerequisites

Install Exporter

Install NetMeter Exporter by following the instructions mentioned in the exporter README.

Configuration

File

The configuration file name for this integration is go.d/prometheus.conf.

You can edit the configuration file using the edit-config script from the Netdata config directory.

cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config go.d/prometheus.conf

Options

The following options can be defined globally: update_every, autodetection_retry.

Name Description Default Required
update_every Data collection frequency. 10 False
autodetection_retry Recheck interval in seconds. Zero means no recheck will be scheduled. 0 False
url Server URL. True
selector Time series selector (filter). False
fallback_type Time series selector (filter). False
max_time_series Global time series limit. If an endpoint returns number of time series > limit the data is not processed. 2000 False
max_time_series_per_metric Time series per metric (metric name) limit. Metrics with number of time series > limit are skipped. 200 False
timeout HTTP request timeout. 10 False
username Username for basic HTTP authentication. False
password Password for basic HTTP authentication. False
proxy_url Proxy URL. False
proxy_username Username for proxy basic HTTP authentication. False
proxy_password Password for proxy basic HTTP authentication. False
method HTTP request method. GET False
body HTTP request body. False
headers HTTP request headers. False
not_follow_redirects Redirect handling policy. Controls whether the client follows redirects. no False
tls_skip_verify Server certificate chain and hostname validation policy. Controls whether the client performs this check. no False
tls_ca Certification authority that the client uses when verifying the server’s certificates. False
tls_cert Client TLS certificate. False
tls_key Client TLS key. False
selector

This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected.

  • Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4)
  • Pattern syntax: selector.
  • Option syntax:
selector:
  allow:
    - pattern1
    - pattern2
  deny:
    - pattern3
    - pattern4
fallback_type

This option allows you to process Untyped metrics as Counter or Gauge instead of ignoring them.

fallback_type:
  counter:
    - metric_name_pattern1
    - metric_name_pattern2
  gauge:
    - metric_name_pattern3
    - metric_name_pattern4

Examples

Basic

Note: Change the port of the monitored application on which it provides metrics.

A basic example configuration.

jobs:
  - name: local
    url: http://127.0.0.1:9090/metrics
HTTP authentication

Note: Change the port of the monitored application on which it provides metrics.

Basic HTTP authentication.

jobs:
  - name: local
    url: http://127.0.0.1:9090/metrics
    username: username
    password: password
HTTPS with self-signed certificate

Note: Change the port of the monitored application on which it provides metrics.

Do not validate server certificate chain and hostname.

jobs:
  - name: local
    url: https://127.0.0.1:9090/metrics
    tls_skip_verify: yes
Multi-instance

Note: When you define multiple jobs, their names must be unique. Note: Change the port of the monitored application on which it provides metrics.

Collecting metrics from local and remote instances.

jobs:
  - name: local
    url: http://127.0.0.1:9090/metrics

  - name: remote
    url: http://192.0.2.1:9090/metrics

Metrics

This collector has built-in grouping logic based on the type of metrics.

Metric Chart Dimension(s) Algorithm
Gauge for each label set one, the metric name absolute
Counter for each label set one, the metric name incremental
Summary (quantiles) for each label set (excluding ‘quantile’) for each quantile absolute
Summary (sum and count) for each label set the metric name incremental
Histogram (buckets) for each label set (excluding ‘le’) for each bucket incremental
Histogram (sum and count) for each label set the metric name incremental

Untyped metrics (have no ‘# TYPE’) processing:

  • As Counter or Gauge depending on pattern match when ‘fallback_type’ is used.
  • As Counter if it has suffix ‘_total’.
  • As Summary if it has ‘quantile’ label.
  • As Histogram if it has ‘le’ label.

The rest are ignored.

Alerts

There are no alerts configured by default for this integration.

Troubleshooting

Debug Mode

To troubleshoot issues with the prometheus collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn’t working.

  • Navigate to the plugins.d directory, usually at /usr/libexec/netdata/plugins.d/. If that’s not the case on your system, open netdata.conf and look for the plugins setting under [directories].

    cd /usr/libexec/netdata/plugins.d/

  • Switch to the netdata user.

    sudo -u netdata -s

  • Run the go.d.plugin to debug the collector:

    ./go.d.plugin -d -m prometheus

Get Netdata

Sign up for free

Want to see a demonstration of Netdata for multiple use cases?

Go to Live Demo