Skip to content

Events overview

Zenoss Cloud includes a rich variety of features and tools for managing, monitoring, analyzing, and creating events. Events are included in dashboards and Smart View pages and are the main attraction in events consoles.

Managing events

An events console displays events associated with all entities in the current time range and tools for managing events. The display includes visualizations and an interactive table.

The dictionary service provides more readable or compact alternatives to computer-generated event field names and detailed descriptions of the fields. Dictionary entries are used wherever event field names are displayed.

In addition, the Zenoss API includes event management resources for updating and annotating events.

Monitoring events

Dashboards provide tiles and options that enable near real-time event monitoring of specific entities or groups of entities.

  • The Event List + Count tile combines the displays a doughnut chart, a table of events, or both.

  • The Map tile displays the location organizers in a dashboard's scope on an interactive map. If an organizer contains entities and the entities have events during the current time range, the tile displays a doughnut chart representing the events.

  • The Top Event Producers tile displays the count of events and the names of the entities that have the greatest number of events reported against them.

To configure a dashboard for near real-time monitoring, set its time range to (for example) the last hour or 3 hours and its refresh interval to 1 minute or 3 minutes.

Analyzing events

You can analyze large or small groups of events and individual events.

  • Smart View pages can include events associated with an entity and its related entities for analyzing patterns during root cause investigations.

  • Dashboard time ranges can be set to any arbitrary value within your data retention period for investigating conditions in the past.

    Note

    For specific details about your organization’s data retention period, contact your Zenoss Support representative by opening a support ticket.

  • In the events console, you can select 2-4 events and compare them side-by-side, and you can display the details of a single event.

Creating events

There are several ways to create events in Zenoss, including programmatically, through the API, and manually.

Most events are created programmatically. External events are solicited (for example, through ZenPacks) or unsolicited (through SNMP traps or syslog). Internal events are created in response to failed pings, threshold evaluations, and other occurrences. Use the action service to create events by specifying an event destination.

The Zenoss API includes a resource for sending events to Zenoss Cloud. Also, the Collection Zone API also provides a resource of sending events.

Additionally, you can manually create events in the Events console.

Create events in the Events console

You can manually create events in the console for testing event mappings, event transformations, and triggers and notifications.

Note

Your account must be assigned the User or Manager role to create events.

To create an event, perform the following steps:

  1. Log in to Zenoss Cloud as a user with the User or Manager role, and then click EVENTS. The Events console opens.

  2. In the toolbar, click the Create Event (plus sign) button to add an event. The Create Event dialog box opens.

    If you don't see the Create Event button in the toolbar, try clicking the Action options (vertical ellipse) button and then select Create Event in the menu that appears.

  3. In the General Information section of the Create Event dialog box, add the following information. The red asterisk in the dialog box indicates a required field.

    Field Description
    Name A name for this event. When combined with Dimensions, this name makes your event unique. This is a required field.
    Type Uniquely identifies the type of event. You might enter a type using the same "name" that you use for systems that have an event ID, such as "linkDown" or "fault-F0157".
    Summary A short description of the event. This is a recommended field.
    Body A long description of the event.
    Severity The event severity level. The default value is Info.
    Status Defines the current state of an event. You can select Default (unknown), Open (event is actively ongoing), Suppressed (event should be suppressed), or Closed (event is known to have subsided). The default value is Open.
    Acknowledged Indicates if the event is acknowledged. You can keep the default value of Unspecified, or select True or False.
    Entity Enter the name of the entity associated with this event.
  4. In the Dimensions section, enter the dimensions associated with this event. Dimensions, when combined with Name, make this event unique. This is a recommended field.

    Use the criteria builder to enter field names and values for the event. The field names must be unique for the event. Both the field name and the value must be strings. Typically, you might enter the same dimensions used for the entity to which the event is related.

  5. (Optional) In the Metadata section, enter the fields associated with this event. The field names must be unique for the event.

    Note

    You can associate the event with a source in either the Dimensions or the Metadata fields. If these fields are not specified, then the source is set as a metadata field to the value of "default".

  6. Click SAVE. A success message appears confirming that your event is created. Optionally, click CANCEL to discard your changes.

If your event isn't created, check that you have entered information in the Name field.