e9af618081
* make the title metadta the H1 * Update collectors/python.d.plugin/zscores/README.md * Update libnetdata/ebpf/README.md * Update ml/README.md * Update libnetdata/string/README.md --------- Co-authored-by: Chris Akritidis <43294513+cakrit@users.noreply.github.com>
2.3 KiB
Export metrics to Prometheus remote write providers
The Prometheus remote write exporting connector uses the exporting engine to send Netdata metrics to your choice of more than 20 external storage providers for long-term archiving and further analysis.
Prerequisites
To use the Prometheus remote write API with storage providers, install protobuf and snappy libraries. Next, reinstall Netdata, which detects that the required libraries and utilities are now available.
Configuration
To enable data exporting to a storage provider using the Prometheus remote write API, run ./edit-config exporting.conf
in the Netdata configuration directory and set the following options:
[prometheus_remote_write:my_instance]
enabled = yes
destination = example.domain:example_port
remote write URL path = /receive
You can also add :https modifier to the connector type if you need to use the TLS/SSL protocol. For example:
remote_write:https:my_instance.
remote write URL path is used to set an endpoint path for the remote write protocol. The default value is /receive.
For example, if your endpoint is http://example.domain:example_port/storage/read:
destination = example.domain:example_port
remote write URL path = /storage/read
You can set basic HTTP authentication credentials using
username = my_username
password = my_password
buffered and lost dimensions in the Netdata Exporting Connector Data Size operation monitoring chart estimate uncompressed
buffer size on failures.
Notes
The remote write exporting connector does not support buffer on failures