From 609a0e13f30922d8fffe34d3589a8465e4b5e5d1 Mon Sep 17 00:00:00 2001 From: Hiroshi Hatake Date: Thu, 2 May 2024 12:17:09 +0900 Subject: [PATCH] Update pipeline/inputs/prometheus-remote-write.md Co-authored-by: Pat Signed-off-by: Hiroshi Hatake --- pipeline/inputs/prometheus-remote-write.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pipeline/inputs/prometheus-remote-write.md b/pipeline/inputs/prometheus-remote-write.md index f8ba7f120..c17f5032b 100644 --- a/pipeline/inputs/prometheus-remote-write.md +++ b/pipeline/inputs/prometheus-remote-write.md @@ -15,7 +15,7 @@ This input plugin allows you to ingest a payload in the Prometheus remote-write | buffer\_max\_size | Specify the maximum buffer size in KB to receive a JSON message. | 4M | | buffer\_chunk\_size | This sets the chunk size for incoming incoming JSON messages. These chunks are then stored/managed in the space available by buffer_max_size. | 512K | |successful\_response\_code | It allows to set successful response code. `200`, `201` and `204` are supported.| 201 | -| tag\_from\_uri | If true, tag will be created from uri. e.g. api\_prom\_push from /api/prom/push. This parameter will be prioritized when tag parameter is specified. If specify as false, it needs to specify user specified tag with tag parameter. | true | +| tag\_from\_uri | If true, tag will be created from uri, e.g. api\_prom\_push from /api/prom/push, and any tag specified in the config will be ignored. If false then a tag must be provided in the config for this input. | true |