Skip to main content

Event Setting

Home > Select Project > Icon Sitemap > Alert > Event configuration New

The new Event setting menu can enhance the user experience by focusing on the field (Field) rather than the category (Category). This event function allows you to quickly apply warning level notifications to users who do not need powerful features such as metric event settings or to repeatedly use simple notification conditions. By providing basic event templates for the products of the created project, you can quickly and easily configure the desired warning notification events.

By selecting fields first rather than categories, we can resolve the discrepancy between metrics perceived by the user and event settings. By combining the visual intuition of the simulation, you can complete event settings quickly and accurately.

Note
  • New projects can use this feature without extra settings. However, for the created projects, select Create event template. The event lists optimized for new features are automatically generated.

  • The provided event templates may differ depending on the product.

  • This function can be used by only the members with the Alert settings role. For more information about the member roles, see the following.

Basic event templates

Basic event templates are provided based on the product of the created project. You can activate a desired event by selecting Activation on the utmost left of the event list.

Event list

The provided event templates are as follows. The default value set in Indicator can be changed to a desired one.

  • Active Sessions

    Category: db_mysql_counter

    If the number of sessions running query (active_sessions) exceeds 30, a warning (Warning) level notification is sent. If it exceeds 50, a critical (Critical) level notification is sent.

  • Lock Wait Sessions

    Category: db_mysql_counter

    If the number of sessions waiting to acquire the row lock (lock_wait_sessions) exceeds 3, a warning (Warning) level notification is sent. If it exceeds 5, a critical (Critical) level notification is sent.

  • Memory

    Category: db_mysql_counter

    If the memory utilization (mem(xos)) exceeds 80%, a warning (Warning) level notification is sent. If it exceeds 95%, a critical (Critical) level notification is sent.

    Note

    This template is only available if you have configured and run the XOS agent. For more information about the XOS agent configuration, see the following.

  • Replication Delay

    Category: db_mysql_counter

    In the case of a replication structure, if the delay time (replication_delay) reflected in the replication DB exceeds 50 seconds, a warning (Warning) level notification is sent. If it exceeds 100 seconds, a critical (Critical) level notification is sent.

Modifying event

You can modify the metric values applied in basic event templates for changing the warning notification occurrence criteria. In addition, you can change the notification occurrence criteria through various option settings. Select Edit icon on the event to modify. The event editing screen appears. Modify the following items and then select Save.

Define event condition

You can set the criteria for event occurrence conditions.

Define event condition

  • RUN: After setting the event conditions, you can simulate the set event by selecting the button.

    Event simulation

  • Indicatorsettings: You can set the thresholds for the Warning or Critical notifications. Set an operator and then enter thresholds.

    • Operators: > (greater than), >= (greater than or equal to), < (less than), <= (less than or equal to), == (equal to)

    • You can enter a positive number, negative number, or 0 as the threshold, but whether to enter a negative number may differ depending on the selected event template.

    Note
    • Depending on the provided event template, the notification levels that can be set may differ.

    • You can select one of Warning and Critical. However, you cannot disable both two items.

  • Consecutive: You can send notifications based on the count that meets the specified event conditions.

    • Not used: Notifications are sent each time any event occurs.

    • Consecutive: Notifications are sent each time any event occurs as many as you specified.

  • Pause: No event occurs for the selected time after receiving the notification.

  • Resolved notifications: When the event is resolved, notify the status of RECOVERED.

Tip

The criteria for sending notifications differ depending on the following conditions:

ConsecutiveResolved notificationsAction
Not usedOnNotifications are sent when the specified event conditions are met or resolved.
OffThe notifications are sent whenever the specified conditions are met.
Consecutive N Occurrences OnNotifications are sent when a condition is met at least N times or an event is resolved at least N times.
OffA notification is sent if the event conditions you set are met more than N times. After sending a notification, the count is reset and it is recounted.

Select event target

You can set to send events that occur only on specific agents as notifications. Click the Agent (Instance) item and then select a desired agent. After selecting the agent, you can additionally select the database name (DbName) of the connected DB server.

Select event target

Note
  • Depending on the provided template, selectable targets may differ.

  • To check the event occurrence status for the selected targets, select RUN in Define event condition.

  • If you do not select a target, notifications are sent to all agents included in the project. When an event occurs across all agents, it can generate numerous notifications.

Basic information and notification setting

You can write a title and message for the event received as a notification, and then select the recipients.

Basic information and notification setting

  • Activate events: You can enable the current events.

  • Event title: The event name of the basic template has been specified. You can edit the event name as you want.

  • Message: The message of the basic template has been specified. You can edit the message as you want. If the time icon button is clicked, you can see the history of previously entered messages.

    Tip

    You can write a message by entering the ${Tag} or ${Field} variable in the message field.

    In Analysis > Metrics Search, select Category and then check the ${Tag} or ${Field} variable that can be entered. For the Category name of the current event template, see the Category in the following

  • Test alert: When receiving notifications as events, you can pre-check the specified event name and message. Testing is possible only when the required items (Indicatorsettings, Event title, and Message) are all entered.

    Note

    During testing, substitution for actual metric values or variables does not work, and the notifications cannot be sent only to users with recipient tags.

  • Event reception: You can select members to receive notifications from current events.

    • Receive all: You can send notifications to all the members in the project.

    • Receive selected tags: It sends notifications to project members and 3rd-party plugins with the selected tags. Click Add tag or to select a tag from the tag list.

    Note

    In Alert > Notifications, you can set the tags in project members and 3rd-party plug-ins. For more information, see the following.

Adding event

You can edit a basic event template to add your own notification.

  1. On the upper right of the screen, select Add alert settings.

  2. Select an event to add from the template list.

  3. Set the options in the Select event target, Select event target, and Basic information and notification setting sections in turn.

  4. After all settings are made, select Save on the upper right of the screen.

You can see newly added events in the event list.

Note
  • To use it differently from basic event templates, edit the Event title item and then save it.

  • For more information about the basic event templates, see the following.

  • For more information about the event condition setting, see the following.

Deleting event

You can delete the embedded or added events.

  1. Select Edit icon in the event to delete from the event list.

  2. In the event modification screen, select Delete on the upper right of the screen.

  3. If the deletion confirmation window appears, select Delete again.

Note

The deleted event cannot be restored.

Modifying to JSON format

You can modify event settings in JSON format.

  1. On the upper right of the screen, select JSON .

  2. When the editing window appears, modify the content in JSON format.

  3. After all changes are made, select Save on the upper right of the screen.

Note

If the modified content does not match the JSON format, an error message appears at the bottom of the screen and the changes cannot be saved. The displayed error message may differ depending on the format.

JSON error

The JSON data structure is as follows:

{
"metaId": "infra001",
"displayName": "CPU",
"stateful": true,
"selectCondition": {},
"warningEnabled": true,
"criticalEnabled": true,
"receiver": [],
"warningThreshold": "cpu > 70",
"criticalThreshold": "cpu > 90",
"repeatCount": 1,
"silentPeriod": 60000,
"enabled": false,
"message": "CPU = ${cpu}"
},

The fields in JSON data are associated with the following options in event settings.

JSON fieldOption
metaIdUnique identifier for the selected template
displayNameEvent title
statefulResolved notifications
selectConditionSelect target
warningEnabledWhether the Warning event is active or not
criticalEnabledWhether the Critical event is active or not
receiverList of key values in the Event reception > Receive selected tags option
warningThresholdThreshold setting of the Warning event
criticalThresholdThreshold setting of the Critical event
repeatCountConsecutive N Occurrences
silentPeriodPause
enabledActivate events
messageMessage

Sharing as a JSON file

You can save event settings as a JSON file to share the settings with other users or import them from other users.

Export

  1. On the upper right of the screen, select JSON .

  2. If the JSON edition window appears, select Export.

  3. Once the JSON file has been downloaded, forward it to others for sharing.

Note

The format of the JSON file name is event-rules-YYYY-MM-DD.json.

Import

  1. On the upper right of the screen, select .

  2. Using the Export function, select a JSON file to download.

  3. If the JSON edition window appears, select Add to list or Overwrite.

Caution

It is recommended to use this function for the products of the same type. You can import event settings from the projects for other products, but it does not work.

Searching event

You can search the event by event name or metric in the event list. Enter a string in the search field and then select Search icon.