Skip to content

Commit

Permalink
in_opentelemetry: add tag_from_uri property (#1275)
Browse files Browse the repository at this point in the history
Signed-off-by: Takahiro Yamashita <nokute78@gmail.com>
nokute78 authored Jan 19, 2024
1 parent 8d87924 commit af41195
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions pipeline/inputs/opentelemetry.md
Original file line number Diff line number Diff line change
@@ -17,6 +17,7 @@ The OpenTelemetry plugin allows you to ingest telemetry data as per the OTLP spe
| 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. v1_metrics from /v1/metrics . | true |

Important note: Raw traces means that any data forwarded to the traces endpoint (`/v1/traces`) will be packed and forwarded as a log message, and will NOT be processed by Fluent Bit. The traces endpoint by default expects a valid protobuf encoded payload, but you can set the `raw_traces` option in case you want to get trace telemetry data to any of Fluent Bit's supported outputs.

0 comments on commit af41195

Please sign in to comment.