Events are generated on monitored resources and may be converted into alerts based on defined criteria. OpsRamp supports event generation for the following resource types:

• VMware
• Cisco HyperFlex
• Cisco UCS
• Citrix Cloud VDA Server
• EMC CLARiiON
• EMC VNX
• Microsoft Hyper-V
• Viptela

Create an Event

You can create events at the Service Provider, Partner and Client scopes. Follow these steps to create an event:

1. Navigate to Setup > Account > Monitoring.

2. Select the Metrics & Events tab.

3. In the Events tab, click +ADD. The ADD EVENT page is displayed.

4. Enter the following field details:

   Field	Description
   Name	Unique name for the event. For details, see the Event name format section.
   Display Name	Unique display name.
   Tag Name	User-defined name for filtering.
   Adapter Type	Select from VMware, Cisco UCS, EMC VNX, etc
   Description	Event description.

5. Click ADD EVENT.
   The event will be available in the list under Events.
   
   Apply the event monitoring template on the resources. Based on the monitoring frequency, OpsRamp converts the events into alerts and shows the alerts in the alert browser.

   Sample alert:

Event name format

The following are acceptable formats for an event name:

• Event names should not contain a dot (.), instead use an underscore (_) between the words.
  hyperflex.cluster.event.ClusterPolicyComplianceFailedEvent is not valid
  hyperflex_cluster_event_ClusterPolicyComplianceFailedEvent is valid
• An event name can have a maximum of ten underscores “_”. An event name cannot start or end with an underscore.
• An event name can contain numeric values (0-9), but cannot start with a numeric value.
• An event name should be case-insensitive.
• The length of the event name should be less than or equal to 255, including underscores.

View Events

You can view the list of all events in the Events page.
The following table provides details of each field.

Update an Event

To update event details:

1. Search for the event using the search icon and click the event name. The event details are displayed.
2. Make the necessary changes and click Save. The event is updated.

Export an Event

The Export functionality allows you to save an event in CSV or JSON format.

Follow these steps to export an event:

1. Search for the event(s) you want to export.
2. Select the event(s) and click Export.
3. Select the required format: JSON or CSV. The event is exported in the selected format.
   

   Note

   If no specific event(s) are selected before exporting, all the available events in the scope will be exported, by default.

Import an Event

The Import functionality allows you to import a CSV or JSON formatted event file as an event. Follow these steps to import an event:

1. In the Events tab, click the Import icon and then click Upload.
2. Select a file to upload. Supported file formats are JSON or CSV.
3. Click Import. The event is imported and the details are shown on the Import Results page.
   If the import fails, a message is displayed with the reason for the failure.

Delete an Event

Permissions

• You must have permission to manage events.

Follow these steps to delete a custom event:

1. Navigate to Setup > Account.

2. Navigate to Monitoring > Metrics & Events card.

3. Click the Events tab.

4. On the Events listing page, search for the event you want to delete.

5. Move hover over the row and click the ellipsis (…) icon.
   
   
   

6. Select Remove.
   
   Before deletion, OpsRamp checks for dependencies to avoid disrupting existing monitoring configurations.
   See Delete a Metric for more information.

   • If there are no dependencies, the event is deleted and a confirmation message appears.

Version History

Configuration version history provides a record of changes made to an event. You can use it to review the current configuration, compare it with an earlier version, and restore a previous version.

Version history is enabled by default for events. A version is created when an event is created or updated.

Permissions

Your access to version history is based on your permissions for the event:

• To view version history, you must have permission to view the event.
• To restore a version, you must have permission to modify or update the event.

Why use version history?

Updating an event, including its display name, tag name, or description, can change how the event is identified and processed. For example, an unintended change to an event’s configuration can cause events to be matched or processed incorrectly, resulting in excessive notifications or false alarms, or can cause genuine issues to go undetected.

Use version history to:

• View snapshots of an event configuration.
• Identify values that changed between versions.
• Compare the current version with an earlier version.
• Compare two older versions.
• Restore a suitable earlier version.

View version history

View the version history of an event to review its current configuration and previously saved versions.

Follow these steps to view an event’s version history:

1. In the Events tab, search for the event whose version history you want to view.
2. Mouse hover over the row and click the ellipsis (…) icon.
3. Select Version History. The Version History page appears with the current event configuration, by default. The dropdown lists the versions with timestamp.
   
   
   
4. Clicking the dropdown lists the available earlier versions.
   
   
   

The dropdown labels the following versions:

• Current Version: The event configuration that is currently active.
• Baseline: The first saved version of the event, created when the event was originally created. It is the starting point of the version history and the oldest version available for comparison or restore.

You can click the versions in the dropdown to review the changes. The selected version displays the event configuration, allowing you to compare it with the current version and identify any values that changed.

Compare versions

Compare event versions to see how configuration changes affect the way events are processed and the alerts they generate. This comparison helps you find what caused unexpected alerts and decide whether to restore an earlier version.

Follow these steps to compare versions:

1. In the Events tab, search for the event whose version you want to compare.
2. Mouse hover over the row and click the ellipsis (…) icon.
3. Select Version History. The Version History page appears with the current event configuration, by default.
4. Click +Compare at the top right corner of the page.
   
   
   By default, the system compares the current version with the version immediately preceding it.
   
   
   The comparison highlights the changes made. Review the differences between the configuration values.

• You can select another older version to compare with the current version, or compare two older versions.

Comparison helps you determine which event configuration change might have caused unexpected alerts or changed how events are processed.

Restore a version

Restore an earlier version of an event when you need to revert recent configuration changes. The restored configuration becomes the current version while preserving the existing version history.

Follow these steps to restore a version:

1. In the Events tab, search for the event.
2. Mouse hover over the row and click the ellipsis (…) icon.
3. Select Version History. The Version History page appears with the current event configuration, by default.
4. Click +Compare at the top right corner of the page.
   
   
   By default, the system compares the current version with the version immediately preceding it.
   
5. From the dropdown on the right, select the version you want to restore.
   
   
   
6. Click Restore. A confirmation message appears.
   
   
   
7. Review the message and click Restore.

Restoring a version creates a new version. Existing versions remain in the version history. After the operation is complete, the restored values become the current configuration.

Version retention and deleted events

Version history is retained only while the event exists.

×