same applications different templates
Hi,
I gave zabbix 1.8.3, after some absence from monitoring tasks, a try.
For what I see it has a good bunch of new features I need to come common with.
One thing wher I was struggling with, in the past, is that it's still not possible to add the same application to different templates.
Question: what is the idea behind linking applications with templates?
I like the general applications like Memory, File, ... as they are because they
look simple and logical to me.
Example:
When I have a rootserver and e.g. a Virtuozzo Container there is a difference because Virtuozzo don't uses swap space.
So I need to move the swap items/trigger to a new template for explicit Root_Server checks. I want the checks to still appear under the Filesystem application but this does not seems to be possible.
The 2 workarounds I see are to a) rename the Application to Rootserver_Filesystem or b) to move all Filesystem checks from the default Linux_Server Template to explicit Templates.
Solution a) involves a lot more work and in worst case leads to inconsistency of checks. b) seems to be the best way, but using different appnames for different hardware can also move to complex setup.
At all, I don't need apps that offer the same meaning but for different hardware. Any oppinion on that?
I gave zabbix 1.8.3, after some absence from monitoring tasks, a try.
For what I see it has a good bunch of new features I need to come common with.
One thing wher I was struggling with, in the past, is that it's still not possible to add the same application to different templates.
Question: what is the idea behind linking applications with templates?
I like the general applications like Memory, File, ... as they are because they
look simple and logical to me.
Example:
When I have a rootserver and e.g. a Virtuozzo Container there is a difference because Virtuozzo don't uses swap space.
So I need to move the swap items/trigger to a new template for explicit Root_Server checks. I want the checks to still appear under the Filesystem application but this does not seems to be possible.
The 2 workarounds I see are to a) rename the Application to Rootserver_Filesystem or b) to move all Filesystem checks from the default Linux_Server Template to explicit Templates.
Solution a) involves a lot more work and in worst case leads to inconsistency of checks. b) seems to be the best way, but using different appnames for different hardware can also move to complex setup.
At all, I don't need apps that offer the same meaning but for different hardware. Any oppinion on that?
Comment