This Question is Answered (go to answer)

4 "helpful" answers available (2 pts)
22,293 Views 9 Replies Last post: Jan 6, 2010 8:14 AM by jmp242 RSS
sykko Rank: White Belt 13 posts since
Aug 4, 2009
Currently Being Moderated

Dec 23, 2009 10:03 AM

User alert (e-mail)

Hi guys,

 

Im trying to figure it out but it seems I missed something.

I got 3 users in Settings>Users. Admin and 2 other users (both as ZenUser)

Admin has no email but other 2 users got email configured in settings.

 

Now, I am experiencing something I dont really understand.

Those users (not Admin) are NOT having any Administered Objects attached, they are not part of any group that is assigned to any device. Simply, there are 2 users, thats all. Now, when any kind of device is going down, or has just an event those users are always receiving an email.

When I started to attach some device to those users (Administered Objects) situation is the same, nothing has changed. Everytime Zenoss counts an event all users are receiving emails.

Alerting rules are Zenoss default:

 

Production State = Production

Severity >= error

Event State = New

 

I just want to manage users to simply send alerts to users attached to the device.

 

Any idea what I missed?

 

Regards

R

Tags: 2.5, alerting, zenuser, e-mail
Andrea Consadori ZenossMaster 636 posts since
Feb 11, 2008
Currently Being Moderated
1. Dec 23, 2009 11:21 AM in response to: sykko
Re: User alert (e-mail)

Hi,

alerting rules is made under "/ZenUsers /admin"

 

address is optional because zenoss by default sent mail to user alerting rules email (i.e. if admin make rule alarm will be sent to his email).

 

you can filter email using filter "Manager is = username" but you've to create 3 rules, 1 for every user.

 

(it's an idea, i don't test it)

phonegi Rank: Green Belt 186 posts since
Apr 15, 2009
Currently Being Moderated
3. Dec 28, 2009 12:01 PM in response to: sykko
Re: User alert (e-mail)

Yes, I got confused about that when I started out with Zenoss too. Administered Objects don't do anything - you need to use Alerting Rules. I think you will find these threads useful:

 

http://community.zenoss.org/message/15967#15967

http://community.zenoss.org/message/39628#39628

 

By default, every user automatically receives every alert. To limit the alerts received by a user, use alerting rules. Within an alerting rule you can create filters.

 

For example, I manage all the phone equipment and the network guys manage all the switches and routers. I created a Group called /Telecom and another called /Network Infrastructure. Each monitored device is assigned to one of the two groups. On our user accounts I created alerting rules that filter by group. I only receive messages of devices that belong to the /Telecom group, they only receive messages of devices from the /Network Infrastructure group.

phonegi Rank: Green Belt 186 posts since
Apr 15, 2009
Currently Being Moderated
6. Dec 29, 2009 9:57 AM in response to: sykko
Re: User alert (e-mail)

sykko, let me help you: throw away the concept of "managed object". As far as I know, it does not exist in Zenoss. There is no way to associate a user with a device. OK? Once you've got that, move on.

 

Every user by default receives notification of every event. However, alerting rules can be used to manipulate what messages are sent and when they are sent. Alerting rules are applied to every event. They use the properties of an event to filter which messages will be sent to the user.

 

The next Zenoss concept you want to understand is groups. Devices can be organized in different ways. Device classes organize devices by hardware type. So all of your network switches might be assigned to the device class /Net/Switch. Your Windows servers can be assigned to /Server/Windows and so on.

 

There are other groupings that are totally arbitrary - they are only there for your convenience. If you navigate to the Edit tab of any device you will see a Systems value and a Groups value. These are available for you to organize devices and most importantly - they assist with alerts. See Chapter 9 of the Adminstration Guide.

 

For instance, as I mentioned earlier, we have two alerting groups - me and the network guys. I get alerts for telecom equipment, they get alerts for network infrastructure. I created one group called /Network Infrastructure and another called /Telecom. In my phone room, I have an environment monitor that is in /Devices/Environmental, and is assigned to /Groups/Telecom. My phone system is in /Devices/PBX and is assigned to /Groups/Telecom. My voicemail server is in /Devices/Server/Windows and is assigned to /Groups/Telecom. Finally, there is a network switch that is in /Devices/Net/Switch and is assigned to /Groups/Telecom AND /Groups/Network Infrastructure.

 

Alerting rules are applied to events. See Jane Curry's Zenoss Event Management paper for more information on events. When an event is created, properties of the device that generated the event are assiged to the event. These can be used in alerting rules.

 

I created an alerting rule in my user account so that I would only receive events that are generated by a device that belongs to the /Telecom group. I did that by creating an alerting rule, then editing it. Just above the Save button is the Add Filter drop down box. I Selected "Device Groups" from the drop down, which added a new filter to my alerting rule. I assigned it as follows "Device Groups is /Telecom". Now any event that is generated by a device not assigned to the /Telecom group is filtered out and not sent to me.

 

There are lots of filter combinations you can use. Once you get the hang of it, the possibilities are endless. I created 2 user accounts for each user - one for their email and another for SMS. The alerting rules are the same except that the email accounts get messages of severity "Info" and above whereas the SMS accounts are only sent severity "Warning" and above. Also, on the SMS accounts, "Warning" messages are only sent during normal business hours, since they aren't emergencies. Messages of severity "Error" and above are sent 24/7.

chitambira Rank: Green Belt 107 posts since
Oct 15, 2008
Currently Being Moderated
8. Jan 6, 2010 4:48 AM in response to: phonegi
Re: User alert (e-mail)

[quote] sykko, let me help you: throw away the concept of "managed object". As far as I know, it does not exist in Zenoss. There is no way to associate a user with a device. OK? Once you've got that, move on.[/quote]

 

This is NOT true. If you configure Administered Objects for a user, that user will be able to:

- Change zProperties for that device

- Change some configuration for that device

- Manage events for that device (class changes, mapping etc)

- Remodel, customise, modify and fifddle with some other aspects of that devices

 

All this is otherwise not possible for any normal user, unless you cange the privileges schema in Zope.

 

However its true that "Administered Objects" has nothing to do with Alerting rules. These two concepts have separate/different functions. Take  a situation where you have a team of Systems administrator and Database administrators, You would want to associate device management (Administered Objects) with specific Sys Admins, and on the Other hand assign different Alerting rules to specific DBAs

jmp242 ZenossMaster 2,304 posts since
Mar 7, 2007
Currently Being Moderated
9. Jan 6, 2010 8:14 AM in response to: chitambira
Re: User alert (e-mail)

Well, yes, that is true. However, in the context of e-mail alerts,

Zenoss doesn't automatically make use of Administered Objects to do

anything with e-mails. I don't recall off hand if you can even filter on

that in an Alerting rule. The way to select which events get sent to a

user by an e-mail is going to be alerting rules, not some setting at the

device.

--

James Pulver

Information Technology Area Supervisor

LEPP Computer Group

Cornell University

 

 

 

chitambira wrote, On 1/6/2010 4:39 AM:

quote sykko, let me help you: throw away the concept of "managed object". As far as I know, it does not exist in Zenoss. There is no way to associate a user with a device. OK? Once you've got that, move on.[/quote]

 

This is NOT true. If you configure Administered Objects for a user, that user will be able to:

- Change zProperties for that device

- Change some configuration for that device

- Manage events for that device

- Remodel, customise, modify and fifddle with some other aspects of that devices

 

All this is otherwise not possible for any normal user, unless you cange the privileges schema in Zope.

>

More Like This

  • Retrieving data ...

Bookmarked By (0)