Terms

Term

Description

Monitoring source

A monitoring source is an upstream monitoring system. Examples include Alibaba Cloud monitoring systems, open source monitoring systems, other cloud provider monitoring systems, and commercial monitoring systems. Alerts from monitoring sources are the origin of all alarms, events, and incidents.

Integration

Integration is the required configuration to connect a monitoring source with O&M Event Center. This product provides detailed steps to help you complete the integration.

Integration key

An integration key is the unique identifier for connecting a monitoring source with O&M Event Center. Each monitoring source integration requires a corresponding integration key.

Term

Description

Policy center

The policy center is the operational hub of O&M Event Center. It includes features for event routing rules and notification subscriptions.

Rule condition

A rule condition is a trigger that distributes alerts from an integrated monitoring source as events or alarms. Alerts that meet the same rule condition are converged and suppressed into a single event or alarm.

For more information, see What are event routing rules?

Time window

A time window is the effective time range in which multiple rule conditions must be met. You only need to set a time window when a rule involves two or more monitoring sources.

Example: Monitoring source A is configured with rule condition 'a', and monitoring source B is configured with rule condition 'b'. The time window is set to 10 minutes. This means the overall condition is met and an event or alarm is distributed only if both of the following occur within a 10-minute period: monitoring source A triggers an alert that meets condition 'a', and monitoring source B triggers an alert that meets condition 'b'. The order in which conditions 'a' and 'b' are met does not matter.

Notification channel

A notification channel is the method used to send notifications when an event, alarm, or incident is triggered. Supported channels include IM group chats (DingTalk and WeCom), phone calls, text messages, and emails.

Notification type

A notification type is a subscription configuration that sends notifications for events, alarms, or incidents to different channels based on their priority and impact level.

For more information, see What are notification subscriptions?

Upgrade policy

An upgrade policy is a set of rules for all events. It defines a series of notification policies with different timings based on event priority and impact level. Flexible and customizable upgrade policies help you promptly follow up on and resolve critical events.

For more information, see What is an upgrade policy?

Term

Description

Alert

All records pushed from monitoring sources to O&M Event Center are called alerts.

Alarm

When alerts from a monitoring source are distributed based on a rule condition and the trigger type is Alarm, the records are called alarms in the product.

For more information, see What is an alarm?

Event

When alerts from a monitoring source are distributed based on a rule condition and the trigger type is Event, the records are called events in the product.

Events have a higher priority than alarms. They are assigned to a specific owner for continuous follow-up, resolution, and archiving.

For more information, see What is an event?

Incident

In daily operations, an incident is any occurrence that causes a service interruption, a degradation in service quality, or a poor user experience. Problems caused by the user's environment or actions are not considered incidents.

Incidents have a higher priority than events. If the impact of an event expands or worsens during handling, the event must be upgraded to an incident for in-depth follow-up.

For more information, see What is an incident?

Term

Description

Service

A service is the smallest unit of business continuity management for an enterprise.

For more information, see What is a service?