Help with grouping/triggers/templates

[barronj]

Hi All.

I've just started with Zabbix, so I think I just need to understand the context of some of these items. I have searched, but have perhaps not come up with specific enough terms, as I haven't found what I'm looking for if it's been previously discussed.

Here's my situation. The pool of machines I'm monitoring are all Windows servers. Many of the things I am interested already exist in the Windows template, and I've already added network checks to that template as well. (Thanks for the many threads on that topic.)

I've just added a few hosts so far, and am about to start adding items and triggers around some items NOT covered by the template, like whether certain specific processes are running, for example.

There are users of these systems who might benefit from access to the "Triggers" overview type on Monitoring-->Overview-->Triggers. However, they are NOT going to want to see ALL the triggers I'm going to set up, they are only going to want to see a subset of those triggers.

Is there some combination of clever group/trigger/template management that I can use such that I can somehow segregate those triggers which those users WILL care about in a way that they can select Monitoring-->Overview-->Triggers and see only that small subset if they choose the right group, but yet still allow me to see an overview of ALL the triggers if I would be logged in and want that view?

Thanks!

[Alexei]

Is there some combination of clever group/trigger/template management that I can use such that I can somehow segregate those triggers which those users WILL care about in a way that they can select Monitoring-->Overview-->Triggers and see only that small subset if they choose the right group, but yet still allow me to see an overview of ALL the triggers if I would be logged in and want that view?

Thanks!

No, it is not possible. The permission system is created to strictly separate one group of hosts from another. No exceptions here.

If you are a Linux administrator, why bother with WIndows problems? If you're interested in Windows, configure ZABBIX to have access to the Windows server. This is the logic ZABBIX tries to follow.

[barronj]

I may not have been clear in what I'm trying to do. Zabbix has access to all the machines that I'm currently monitoring or will monitor. I'm not a Linux admin, I'm a Linux novice, but have chosen to build a Linux box here specifically for running Nessus and Zabbix.

What I'm trying to affect is the presentation of the trigger statuses via the Zabbix interface, not to actually limit access for Zabbix to any of these machines.

I'm essentially trying to come up with a way for Zabbix to present an overview screen to a small group of engineering users regarding the machines they care about, without having that overview contain ALL possible information about those machines. This isn't about not allowing them to see something they shouldn't, it's about trying not to overload them with more info than they need.

[barronj]

After thinking about this overnight, and playing with Screens a bit, I guess what I'm really asking is whether I can create a screen with a custom "trigger overview" -- picking and choosing which triggers to display.

If it just can't be done, I can accept that, I just want to be clear in what I'm asking for.

Thanks!

[ttherkelsen]

After thinking about this overnight, and playing with Screens a bit, I guess what I'm really asking is whether I can create a screen with a custom "trigger overview" -- picking and choosing which triggers to display.

If it just can't be done, I can accept that, I just want to be clear in what I'm asking for.

Thanks!

I would be very interested in the answer to the above question, too, because I couldn't find any way to customise the "Triggers Overview" screen component.

I ended up adding a new trigger overview component which only lists the triggers/servers there are problems with in order to get an overview which is actually an overview and not information overkill. If you're interested in this functionality let me know and I'll provide a patch against 1.4.4.

[Alexei]

Perhaps you are interested in a trigger overview for a selected host group only?