I am somewhat new to Zabbix and I am trying to determine the best way to approach monitoring multiple instances of the same application running on a host. I want to monitor the status of an application and have Zabbix trigger a problem when the application is not running or there is a problem with it. I know how to do that but I am running multiple instances of the same application each processing a different data set. Each instance of the application does have a unique identifier so I am able to distinguish between them. However, there can be 15 or more instances running on a host. I don't want to have to manually set up an item and trigger for each instance so I am trying to determine that best way to configure this to make the setup and maintenance simpler.
I want a unique problem alert for each application instance when it is not running or has a problem. I could write a script that would check all of the instances running on a host that could then be used to generate a problem alert when there was a problem. But this would mean that when the a problem was triggered for one application instance if another application instance had a problem while the initial problem was still active there would not be a new separate problem alert for the other application instance.
So basically, I am looking for the best way to setup this up so each application instance will have their own problem alert but the configuration of the items and triggers would not overly cumbersome. Multiple hosts can be running multiple instances of this same application, but all will have a unique name. Which instances are running on a host can also change over time when we need to rebalance and optimize the resources and performance of a host. All of the hosts are Windows if this makes any difference.
I want a unique problem alert for each application instance when it is not running or has a problem. I could write a script that would check all of the instances running on a host that could then be used to generate a problem alert when there was a problem. But this would mean that when the a problem was triggered for one application instance if another application instance had a problem while the initial problem was still active there would not be a new separate problem alert for the other application instance.
So basically, I am looking for the best way to setup this up so each application instance will have their own problem alert but the configuration of the items and triggers would not overly cumbersome. Multiple hosts can be running multiple instances of this same application, but all will have a unique name. Which instances are running on a host can also change over time when we need to rebalance and optimize the resources and performance of a host. All of the hosts are Windows if this makes any difference.
Comment