template_app_elasticsearch_zabbix6.yaml
template_app_elasticsearch_zabbix6_active.yaml
[ZBXNEXT-9559] Change Elasticsearch templates and also create active template Created: 2024 Oct 18 Updated: 2024 Oct 19 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | None |
| Affects Version/s: | 7.0.4 |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Trivial |
| Reporter: | Evren Yurtesen | Assignee: | Zabbix Integration Team |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | Elasticsearch, activeagent, passive, template | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
template_app_elasticsearch_zabbix6.yaml
template_app_elasticsearch_zabbix6_active.yaml
|
| Description |
|
Currently Elasticsearch template uses `HTTP_AGENT` which is executed by Zabbix Server But it can use `web.page.get`. Then it can be used with active and passive agents. I am attaching examples that I modified from a Zabbix 6 installation (although exported from Zabbix7). But perhaps my example does not have the latest changes to the template. So one must adapt from the latest version. (I am just not sure how to deal with UUIDs in that case) As an added advantage, the active checks can access the cluster node from `localhost`. This way, this template can have both active and passive versions and it won't require additional ports to open for monitoring etc. Any zabbix agent can be used to monitor the cluster. I believe this change would benefit the Zabbix/Elasticsearch users? or perhaps provide 3 different templates? HTTP_AGENT, passive and active? |