Agent and agent2 on the same host with active checks

[pmarini]

I'm noticing some issues in the following scenario:

• host is monitored via Agent 2 configured in active mode for the Redis template (Redis by Zabbix Agent 2)
• host is monitored via Agent configured in active mode for the MySQL template (Mysql by Zabbix Agent)

When both are enabled it seems that Agent is trying to send some metrics about Redis to the server

151:20240624:131710.593 active check "redis.ping["unix:///var/run/redis/redis-server.sock"]" is not supported: Unsupported item key.
151:20240624:131710.593 active check "redis.slowlog.count["unix:///var/run/redis/redis-server.sock"]" is not supported: Unsupported item key.
151:20240624:131710.593 active check "redis.config["unix:///var/run/redis/redis-server.sock"]" is not supported: Unsupported item key.
151:20240624:131710.593 active check "redis.info["unix:///var/run/redis/redis-server.sock"]" is not supported: Unsupported item key.



While Agent2 is trying to send some metrics about Mysql to the server:

2024/06/24 13:35:51.003405 check 'mysql.get_status_variables["127.0.0.1","3306"]' is not supported: Cannot fetch data: Cannot fetch data: Error 1045 (28000): Access denied for user '3306'@'localhost' (using password: NO).

So, it seems that each agent is trying to take care of a template that it is not supposed to handle. No particular issues have been noticed when at least one of the agent is configured to use passive checks

Is this setup, agent and agent2 on the same host with active checks, supported?

[cyber]

I hope your host has multiple agent interfaces configured and agents are configured to run on different ports?

[Markku]

Ensure that both agents are named uniquely. That way they will both get their own items, not the same items both.

Markku

[pmarini]

Thank you both for your feedback and sorry for the late reply.

For sure there were one interface/port per agent, but I cannot ensure now that there was no name conflict.

Since then I switched to a Redis template based on Agent, basically because Redis by Zabbix Agent 2 doesn't support authentication (see https://support.zabbix.com/browse/ZBXNEXT-7121), but this is another topic.

I'll make sure to post here any findings if I test the same scenario in the future.