mirror of
https://github.com/netdata/netdata.git
synced 2025-04-16 10:31:07 +00:00
a726c905bd
* First pass of changing netdata to Netdata * Second pass of netdata -> Netdata * Starting work on netdata with no whitespace after * Pass for netdata with no whitespace at the end * Pass for netdata with no whitespace at the front
30 lines
1.5 KiB
Markdown
30 lines
1.5 KiB
Markdown
# Prometheus remote write backend
|
|
|
|
## Prerequisites
|
|
|
|
To use the prometheus remote write API with [storage providers](https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage) [protobuf](https://developers.google.com/protocol-buffers/) and [snappy](https://github.com/google/snappy) libraries should be installed first. Next, Netdata should be re-installed from the source. The installer will detect that the required libraries and utilities are now available.
|
|
|
|
## Configuration
|
|
|
|
An additional option in the backend configuration section is available for the remote write backend:
|
|
|
|
```
|
|
[backend]
|
|
remote write URL path = /receive
|
|
```
|
|
|
|
The default value is `/receive`. `remote write URL path` is used to set an endpoint path for the remote write protocol. For example, if your endpoint is `http://example.domain:example_port/storage/read` you should set
|
|
|
|
```
|
|
[backend]
|
|
destination = example.domain:example_port
|
|
remote write URL path = /storage/read
|
|
```
|
|
|
|
`buffered` and `lost` dimensions in the Netdata Backend Data Size operation monitoring chart estimate uncompressed buffer size on failures.
|
|
|
|
## Notes
|
|
|
|
The remote write backend does not support `buffer on failures`
|
|
|
|
[]()
|