2022-02-04 18:12:24 +01:00
## `http` sink
The `http` sink uses POST requests to a HTTP server to submit the metrics in the InfluxDB line-protocol format. It uses JSON web tokens for authentification. The sink creates batches of metrics before sending, to reduce the HTTP traffic.
### Configuration structure
```json
{
"< name > ": {
"type": "http",
"meta_as_tags" : true,
2022-02-10 13:12:32 +01:00
"url" : "https://my-monitoring.example.com:1234/api/write",
"jwt" : "blabla.blabla.blabla",
2022-02-08 18:06:07 +01:00
"timeout": "5s",
"max_idle_connections" : 10,
2022-02-10 13:12:32 +01:00
"idle_connection_timeout" : "5s",
"flush_delay": "2s",
2022-05-04 13:05:10 +02:00
"batch_size" : 100
2022-02-04 18:12:24 +01:00
}
}
```
- `type` : makes the sink an `http` sink
- `meta_as_tags` : print all meta information as tags in the output (optional)
2022-02-10 13:12:32 +01:00
- `url` : The full URL of the endpoint
- `jwt` : JSON web tokens for authentification (Using the *Bearer* scheme)
2022-02-08 18:06:07 +01:00
- `timeout` : General timeout for the HTTP client (default '5s')
- `max_idle_connections` : Maximally idle connections (default 10)
2022-02-10 13:12:32 +01:00
- `idle_connection_timeout` : Timeout for idle connections (default '5s')
- `flush_delay` : Batch all writes arriving in during this duration (default '1s', batching can be disabled by setting it to 0)
2022-05-04 13:05:10 +02:00
- `batch_size` : Maximal number of batched metrics. Either it is flushed because batch size or the `flush_delay` is reached