|
|
Want to know more about Packt's Article Network? Interested in contributing your article ideas? Please visit our FAQ for more information. See More BROWSE
All Titles WordPress Web Services SOA BPEL Web Graphics & Video Web Development RAW Portugues, Espanol, Italiano, French PHP/MySQL Oracle Open Source Networking & Telephony Moodle Microsoft & .NET Linux Servers jQuery Joomla! JBoss Java e-Learning e-Commerce Dynamics Drupal CRM Cookbook Content Management Beginner Guides Architecture and Analysis AJAX Future Titles Recently Published Titles Philosophy: A route of many roads leading from nowhere to nothing. While it appears that Ambrose Bierce has a little respect for Philosophy in general, he would surely refer to calling routing as—roads leading from a single point to multiple points, or something similar. The purpose of the "Calling Rules" is to define the methodology by which calls are routed from the PBX to the outbound world. This article by Nir Simionovich deals with the routing rules in AsteriskNOW and the Calling Rules tables. See More |
User Management in Zenoss
User Accounts and their PropertiesWorking as the non-admin user has several benefits:
Let's add a new user:
The new user name is added to the list of users (see following screenshot) along with columns for Email address, Pager, address, and Roles.
Before a new user can log in, we must specify a password. To create a password and configure the account, edit the user account by clicking on the user name from the Users table. The following table includes the fields we can set via the Edit Screen.
We use roles to define a user's level of access to the system. The following table lists the available roles from the most to the least restrictive access.
Zenoss Core Network and System Monitoring
Administered ObjectsFor each user, we can assign a list of administered objects, which includes devices, systems, groups, and locations. By matching users to administered objects, we have an easy way to identify who is responsible for the object. The following screenshot shows the Administered Objects for a user.
To add an object, choose the appropriate option from the Administered Objects page menu. If we add a device, the Add Device dialog box filters the list of devices as we type. If we add a system, group, or location, we choose the object from a drop-down list. Each administered object has a default role that we can change. We specify the user's default admin role on each user's Edit tab. If we click on the object name, Zenoss displays the Status page for the device, system, group, or location. Each object also has an Administration page that lists the users identified as administrators. For example, navigate to a device and select More > Administration from the page menu to see the list of administrators for the device.
From the Administrators table of the object (see the previous screenshot), we see a list of users and Roles. Click on the user name to navigate back to the user's Edit page. Event ViewsZenoss enables us to create custom event views per user. To define a custom event view for a user:
Each event view displays columns for type and event summary. By default, the newly created event view looks identical to the Event Console. Click on the name from the Event Views list to display and edit the view (see the following screen capture).
From the edit tab, we specify the following event view properties:
After we edit the view, click Save. Then click on the View tab so that the view gets displayed. Alerting RulesWe attach alerts to users or groups of users. We'll cover groups in the next section, but for now, we'll add an alerting rule at the user level. To add an alerting rule, select the Alerting Rules tab (see the following screenshot) while editing the user name to display the list of rules assigned to the user.
The Alerting Rules table displays a summary of each rule including columns for Name, Delay, Repeat Time, Action, Enabled, and Send Clear. To add a new alerting rule:
The default rule sends an email when any device in a Production State generates a new event with a Severity level equal to or greater than Error. Zenoss also sends an alert when the event clears. However, the alert is disabled by default. Let's take a look at each of the Alerting Rule properties:
An event filter consists of three parts: an event field, a comparison operator, and a value to compare to the event field. We add a filter by selecting the event field from the Add Filter drop-down list. See Appendix A for a list of fields. Next, we specify a comparison operator, such as greater-than and less-than. Then we specify a value to match against the operator. The more filters we add to a rule, the more specific our alerting rule becomes. Books from Packt Alert EscalationsBy using the filters on an alerting rule, we can create an alert hierarchy that notifies another user when a certain condition occurs. We can create a new rule for a second user and add a filter that specifies a count value so that if the event is not acknowledged, the user is notified. For example, if our new filter specifies a count greater than five, we define a rule that does not trigger unless an event remains unacknowledged for five consecutive times. MessageWhile editing our alerting rule, we have the ability to customize the text of the alert message Zenoss sends. To view the Message, click on the Message tab.
We can specify the Subject and the Body for both the down alert and the clear alert. As the text at the bottom of the Message tab indicates, the "message format is a Python format string. Fields are specified as %(fieldname)s." (refer to the previous screenshot). All the event fields are listed for reference. If we set the alerting rule to send a page, we can only specify a subject line for the down and clear alerts because of likely character restrictions on the pager. ScheduleWe may set a schedule for each alerting rule so that the rule sends alerts only during the specified period. From the Edit tab of an alerting rule, click on the Schedule tab to view the Active Periods table. The Active Periods table displays a list of schedules sorted by Name with columns for Start, Duration, Repeat, and Enabled, as shown in the next screen capture.
To add a schedule, select Add Rule Window from the Active Periods table menu. Enter a descriptive name when prompted. Click OK to add the new schedule to the Active Periods table. Click on the name to display the active period's Status page.
On the Status page for the active period, we define the time of day when the alerting schedule is active (see the previous screenshot). The following table lists the available settings.
We may add as many active periods to an alerting rule as we need to accommodate each user's work schedule. GroupsWe've just learned how to define alerting rules on a per user basis, but if we have more than two or three users, we need a better way to handle our alerting rules. Fortunately, Zenoss provides groups, and the same alerting rule concepts that apply to users apply to groups. We start by adding a new group to the Groups table of the Users tab in the Settings page. Next, we assign users to the group in the following way:
Now that we have a newly created group with users assigned, click on the group name to display the group's Edit tab. From the Edit tab, we can add and remove users from our group. On the Administered Objects tab, we identify the relationship a device, system, group, or location has to a group. To begin adding alerting rules for the group, select the Alerting Rules tab and follow the steps outlined in the previous section for individual users. SummaryThis article described managing user accounts, and also roles and the privileges associated with them. We also discussed administered objects, custom event views, alerts and groups. Zenoss Core Network and System Monitoring
About the AuthorMichael Badger is a technical writer with a BS in Technical and Professional Communication from the Pennsylvania College of Technology/Penn State. For 15 years, he has bridged the communication gap between developers and users and specializes in helping users understand, troubleshoot, and use technology.Books from Packt | See More TOP TITLES ![]()
|
| ||||||||