From 335decf6ad7fdf0ed87626d3dd4fec5c6a290212 Mon Sep 17 00:00:00 2001 From: Adrian Lopez Date: Wed, 24 Jan 2024 15:18:06 +0100 Subject: [PATCH] LLD behaviour docs extended --- plugins/outputs/zabbix/README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/plugins/outputs/zabbix/README.md b/plugins/outputs/zabbix/README.md index f1bfbcbbaa5ae..50e3f618816e1 100644 --- a/plugins/outputs/zabbix/README.md +++ b/plugins/outputs/zabbix/README.md @@ -211,13 +211,13 @@ Will generate this Zabbix metric: {"host": "hostname", "key": "telegraf.measurement.value[999,111]", "value": "0"} ``` -## Zabbix low level discovery +## Zabbix low-level discovery Zabbix needs an `item` created before receiving any metric. In some cases we do not know in advance what are we going to send, for example, the name of a container to send its cpu and memory consumption. -For this case Zabbix provides [low level discovery][lld] that allow to create +For this case Zabbix provides [low-level discovery][lld] that allow to create new items dinamically based on the parameters sent by the trap. As explained previously, this output plugin will format the Zabbix key using @@ -228,6 +228,10 @@ Zabbix agent, collecting information about which tags has been seen for each measurement and periodically sending a request to a discovery rule with the collected data. +Keep in mind that, for metrics in this category, Zabbix will discard them until the +low-level discovery (LLD) data is sent. +Sending LLD to Zabbix is a heavy-weight process and is only done at the interval per the lld_send_interval setting. + [lld]: https://www.zabbix.com/documentation/current/manual/discovery/low_level_discovery ### Design