mirror of
https://github.com/Icinga/icinga2.git
synced 2025-07-28 16:14:09 +02:00
Merge pull request #10513 from martialblog/docs/elastic-perfdata
docs: Mention field mapping issue with ElasticsearchWriter
This commit is contained in:
commit
0a08fcc0e1
@ -1229,6 +1229,11 @@ Configuration Attributes:
|
|||||||
Note: If `flush_threshold` is set too low, this will force the feature to flush all data to Elasticsearch too often.
|
Note: If `flush_threshold` is set too low, this will force the feature to flush all data to Elasticsearch too often.
|
||||||
Experiment with the setting, if you are processing more than 1024 metrics per second or similar.
|
Experiment with the setting, if you are processing more than 1024 metrics per second or similar.
|
||||||
|
|
||||||
|
> **Note**
|
||||||
|
>
|
||||||
|
> Be aware that `enable_send_perfdata` will create a new field mapping in the index for each performance data metric in a check plugin.
|
||||||
|
> Elasticsearch/OpenSearch have a maximum number of fields in an index. The default value is usually 1000 fields. See [mapping settings limit](https://www.elastic.co/guide/en/elasticsearch/reference/8.18/mapping-settings-limit.html)
|
||||||
|
|
||||||
Basic auth is supported with the `username` and `password` attributes. This requires an
|
Basic auth is supported with the `username` and `password` attributes. This requires an
|
||||||
HTTP proxy (Nginx, etc.) in front of the Elasticsearch instance. Check [this blogpost](https://blog.netways.de/2017/09/14/secure-elasticsearch-and-kibana-with-an-nginx-http-proxy/)
|
HTTP proxy (Nginx, etc.) in front of the Elasticsearch instance. Check [this blogpost](https://blog.netways.de/2017/09/14/secure-elasticsearch-and-kibana-with-an-nginx-http-proxy/)
|
||||||
for an example.
|
for an example.
|
||||||
@ -1680,11 +1685,11 @@ Configuration Attributes:
|
|||||||
flush\_threshold | Number | **Optional.** How many data points to buffer before forcing a transfer to InfluxDB. Defaults to `1024`.
|
flush\_threshold | Number | **Optional.** How many data points to buffer before forcing a transfer to InfluxDB. Defaults to `1024`.
|
||||||
enable\_ha | Boolean | **Optional.** Enable the high availability functionality. Only valid in a [cluster setup](06-distributed-monitoring.md#distributed-monitoring-high-availability-features). Defaults to `false`.
|
enable\_ha | Boolean | **Optional.** Enable the high availability functionality. Only valid in a [cluster setup](06-distributed-monitoring.md#distributed-monitoring-high-availability-features). Defaults to `false`.
|
||||||
|
|
||||||
Note: If `flush_threshold` is set too low, this will always force the feature to flush all data
|
> **Note**
|
||||||
to InfluxDB. Experiment with the setting, if you are processing more than 1024 metrics per second
|
>
|
||||||
or similar.
|
> If `flush_threshold` is set too low, this will always force the feature to flush all data
|
||||||
|
> to InfluxDB. Experiment with the setting, if you are processing more than 1024 metrics per second
|
||||||
|
> or similar.
|
||||||
|
|
||||||
### Influxdb2Writer <a id="objecttype-influxdb2writer"></a>
|
### Influxdb2Writer <a id="objecttype-influxdb2writer"></a>
|
||||||
|
|
||||||
|
@ -364,7 +364,8 @@ The following event types are written to Elasticsearch:
|
|||||||
* icinga2.event.notification
|
* icinga2.event.notification
|
||||||
|
|
||||||
Performance data metrics must be explicitly enabled with the `enable_send_perfdata`
|
Performance data metrics must be explicitly enabled with the `enable_send_perfdata`
|
||||||
attribute.
|
attribute. Be aware that this will create a new field mapping in the index for each performance data metric in a check plugin.
|
||||||
|
See: [ElasticsearchWriter](09-object-types.md#objecttype-elasticsearchwriter)
|
||||||
|
|
||||||
Metric values are stored like this:
|
Metric values are stored like this:
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user