enable-feature=remote-write-receiver #13090
Replies: 2 comments 6 replies
-
|
Beta Was this translation helpful? Give feedback.
-
That means that your Prometheus server receives samples out of order. You should find out why you send samples out of order. If it is legitimate, you can set an |
Beta Was this translation helpful? Give feedback.
-
I can't get this working at all. I have tried in both the systemd file and the Prometheus config file:
global:
scrape_interval: 15s
scrape_timeout: 10s
evaluation_interval: 15s
alerting:
alertmanagers:
enable_http2: true
scheme: http
timeout: 10s
api_version: v2
static_configs:
scrape_configs:
honor_timestamps: true
scrape_interval: 15s
scrape_timeout: 10s
metrics_path: /metrics
scheme: http
follow_redirects: true
enable_http2: true
static_configs:
remote_write:
remote_timeout: 30s
follow_redirects: true
enable_http2: true
queue_config:
capacity: 10000
max_shards: 50
min_shards: 1
max_samples_per_send: 2000
batch_send_deadline: 5s
min_backoff: 30ms
max_backoff: 5s
metadata_config:
send: true
send_interval: 1m
max_samples_per_send: 2000
Still get the same result:
curl -X POST http://localhost:9090/api/v1/write
remote write receiver needs to be enabled with --web.enable-remote-write-receiver
Beta Was this translation helpful? Give feedback.
All reactions