Skip to main content

Application Event Configuration (Classic)

Home > Select project > Alert icon Alert > Event Configuration classic

You can configure alert notifications based on conditions such as server resource usage (CPU, memory, disk), number of active transactions, transaction errors, and increased response time.

Note

The classic event configuration is a separated menu that allows continued use of the legacy event configuration method.
For more advanced features, use Event configuration.

Default options​

Inactive agent alert​

An event occurs when no data is received from an agent for the configured period. You can enable or disable this feature using the toggle button.

  • Toggle on icon Enabled: An inactive agent event occurs when no data is received for a certain period.

  • Toggle off icon Disabled: No event occurs regardless of data reception status.

Note

The legacy inactive agent check interval can be configured under Management > Agent list.

Send notification when event is resolved​

After an event occurs due to threshold conditions, you can choose whether to send a Recovered notification when the state returns to normal. Use the toggle button to enable or disable this feature.

  • Toggle on icon Enabled: Events operate in a state based manner. When thresholds are exceeded, the status becomes ongoing, and when values recover below thresholds, the status changes to recovered.

  • Toggle off icon Disabled: A one time event occurs each time the threshold is exceeded.

Duplicate agent alert​

If two or more agents with the same name run simultaneously, normal monitoring may be affected, so an event is generated. However, duplicate agent events do not occur again within the configured time window.

  • To check whether agent names are duplicated, review the related options in the Event Configuration menu.

  • Available durations: 30 seconds, 1 minute, 3 minutes, 5 minutes, 10 minutes

Conditions​

You can configure event trigger conditions per item. Input formats vary depending on the item.

Condition (%)

Set two threshold levels: Warning and Critical.
Alerts are triggered when thresholds are exceeded, with Critical taking priority.

  • Left value: Warning threshold (Warning)
  • Right value: Critical threshold (Critical)

Duration​

An event occurs when the configured condition persists for the selected duration.

  • Available durations: 5 seconds, 10 seconds, 15 seconds, 30 seconds, 1 minute, 2 minutes, 3 minutes, 5 minutes, 10 minutes, 30 minutes, 1 hour

Silence​

After an event occurs, no additional events with the same condition occur during the selected silence period. Setting an appropriate silence duration helps prevent excessive alerts.

  • Available durations: 1 minute, 2 minutes, 3 minutes, 5 minutes, 10 minutes, 30 minutes, 1 hour, 2 hours, 3 hours, 6 hours, 12 hours, 1 day

Event enablement​

You can control event behavior using the toggle button.

  • Toggle on icon Enabled: An event occurs when the configured conditions are met.

  • Toggle off icon Disabled: Conditions are not evaluated.

Event configuration​

You can configure events for the following items to monitor system status in real time. After configuring each item, click the Save button at the top right of the screen.

Server CPU / Server memory / Server disk​

An event occurs when server resource usage exceeds the configured threshold (%). You can set different thresholds for Warning and Critical levels.

  • Example: If CPU usage is set to Warning: 80% and Critical: 90%, a Critical event occurs when usage exceeds 90%.

Active transactions​

Monitors the number of transactions currently being processed. An event occurs when the count exceeds the configured threshold and persists for the configured duration. This is useful for detecting situations with a large number of concurrent transactions.

  • Default occurrence count: 100

Transaction errors​

Transactions that do not complete normally are treated as errors. An event occurs when the error count exceeds the configured threshold and persists.

  • Collection interval: 5 seconds

Transaction response time​

Events are configured based on the time required for each transaction to complete (response time). You can detect service slowdowns relative to expected response time.

  • Example: If the response time threshold is 10 seconds and the count threshold is 10
    “An event occurs when 10 or more transactions exceed 10 seconds and the condition persists for 5 seconds.”
Last updated on