mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-21 14:44:00 +00:00
docs: explicitly mention errors processing for import APIs (#4583)
Signed-off-by: hagen1778 <roman@victoriametrics.com>
This commit is contained in:
parent
0e4b883341
commit
922bbabd25
3 changed files with 21 additions and 18 deletions
13
README.md
13
README.md
|
@ -1165,14 +1165,15 @@ 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.
|
||||
|
||||
### How to import data in JSON line format
|
||||
|
||||
`/api/v1/import` is an API optimized for performance and processes data in a streaming fashion.
|
||||
The client can transfer unlimited amount of data through one open connection.
|
||||
`/api/v1/import` API doesn't return parsing errors to the client, as it is expected for data stream
|
||||
to be not interrupted. Instead, look for parsing errors on server side (VictoriaMetrics single-node or vminsert) or
|
||||
Please note, most of the ingestion APIs (except [Prometheus remote_write API](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remote_write))
|
||||
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.
|
||||
Instead, look for parsing errors on the server side (VictoriaMetrics single-node or vminsert) or
|
||||
check for changes in `vm_rows_invalid_total` (exported by server side) metric.
|
||||
|
||||
### How to import data in JSON line format
|
||||
|
||||
Example for importing data obtained via [/api/v1/export](#how-to-export-data-in-json-line-format):
|
||||
|
||||
```console
|
||||
|
|
|
@ -1168,14 +1168,15 @@ 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.
|
||||
|
||||
### How to import data in JSON line format
|
||||
|
||||
`/api/v1/import` is an API optimized for performance and processes data in a streaming fashion.
|
||||
The client can transfer unlimited amount of data through one open connection.
|
||||
`/api/v1/import` API doesn't return parsing errors to the client, as it is expected for data stream
|
||||
to be not interrupted. Instead, look for parsing errors on server side (VictoriaMetrics single-node or vminsert) or
|
||||
Please note, most of the ingestion APIs (except [Prometheus remote_write API](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remote_write))
|
||||
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.
|
||||
Instead, look for parsing errors on the server side (VictoriaMetrics single-node or vminsert) or
|
||||
check for changes in `vm_rows_invalid_total` (exported by server side) metric.
|
||||
|
||||
### How to import data in JSON line format
|
||||
|
||||
Example for importing data obtained via [/api/v1/export](#how-to-export-data-in-json-line-format):
|
||||
|
||||
```console
|
||||
|
|
|
@ -1176,14 +1176,15 @@ 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.
|
||||
|
||||
### How to import data in JSON line format
|
||||
|
||||
`/api/v1/import` is an API optimized for performance and processes data in a streaming fashion.
|
||||
The client can transfer unlimited amount of data through one open connection.
|
||||
`/api/v1/import` API doesn't return parsing errors to the client, as it is expected for data stream
|
||||
to be not interrupted. Instead, look for parsing errors on server side (VictoriaMetrics single-node or vminsert) or
|
||||
Please note, most of the ingestion APIs (except [Prometheus remote_write API](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remote_write))
|
||||
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.
|
||||
Instead, look for parsing errors on the server side (VictoriaMetrics single-node or vminsert) or
|
||||
check for changes in `vm_rows_invalid_total` (exported by server side) metric.
|
||||
|
||||
### How to import data in JSON line format
|
||||
|
||||
Example for importing data obtained via [/api/v1/export](#how-to-export-data-in-json-line-format):
|
||||
|
||||
```console
|
||||
|
|
Loading…
Reference in a new issue