zabbix agent master/slave-how???

[yogi]

Hi,
I have zabbix agent (dockerized) that monitor all my other docker containers.
When a new container is up a trigger is activated ("new container is up") followed by an action.
Now i have a problem: if my zabbix agent docker contianer is down and i am deploying it again, then zabbix agent start to collect data again and recognized all the already running containers as new once and activate the trigger ("new container is up") followed by an action. This is wrong.
How can i prevent it? can i do a master/slave agent?

[jan.garaj]

Generic answer: name your container (--name <container_name>) and then use that <container_name> ("human name"/HCONTAINERID) in your Zabbix template instead of container id, which is regenerated all the time.

To see more details pls visit README https://github.com/monitoringartist/...ker-monitoring (keywords HCONTAINERID, FCONTAINERID).

[yogi]

docker 1.13 swarm-no have container name

I am using docker 13 and don't have a container name, only service name.