From 5702b354a7cdc220c8dfd6c563c65af323eb80b3 Mon Sep 17 00:00:00 2001 From: Roman Khavronenko Date: Tue, 1 Oct 2024 13:39:40 +0200 Subject: [PATCH] docs: add note that otel is not using streaming parsing (#7148) ### Describe Your Changes Please provide a brief description of the changes you made. Be as specific as possible to help others understand the purpose and impact of your modifications. ### Checklist The following checks are **mandatory**: - [ ] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: hagen1778 --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index e898268b5e..5b2f2600a9 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1356,7 +1356,7 @@ Additionally, VictoriaMetrics can accept metrics via the following popular data * `/api/v1/import/prometheus` for importing data in Prometheus exposition format and in [Pushgateway format](https://github.com/prometheus/pushgateway#url). See [these docs](#how-to-import-data-in-prometheus-exposition-format) for details. -Please note, most of the ingestion APIs (except [Prometheus remote_write API](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remote_write)) +Please note, most of the ingestion APIs (except [Prometheus remote_write API](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remote_write) and [OpenTelemetry](#sending-data-via-opentelemetry)) are optimized for performance and processes data in a streaming fashion. It means that client can transfer unlimited amount of data through the open connection. Because of this, import APIs may not return parsing errors to the client, as it is expected for data stream to be not interrupted.