Alert Notifications

Home > Select Project > Alert > Event Configuration > Transaction tab

Transaction events provide fine-grained monitoring of transactions based on specific URLs, errors, status codes, and more. When transactions that meet the configured conditions are detected, an event is triggered. Transaction data is analyzed in 1-minute intervals, and notifications are sent when the number of transactions that satisfy the conditions exceeds the defined threshold.

Latest Agent Versions

To use transaction events, you must install an agent that meets or exceeds the minimum supported version.

Language	Minimum Supported Version
Java	2.2.50 or later
PHP	Not specified (use the latest version or contact support)
Node.js	0.5.21 or later
Python	1.7.8 or later
.NET	2.3.5 or later
Go	Not specified (use the latest version or contact support)

Default Options

• Event Level: Indicates the severity of the event and is classified into three levels: Info, Warning, and Critical.
• Search: Search for events by event name or event reception tag.
• + Add Event: Add a new transaction event.
• Resize Columns: Drag the boundary of each column to adjust its width.

Table | Transaction Event List Structure

Item	Description
No.	Event sequence number
	Whether the event is enabled - Enabled: The event is triggered when conditions are met - Disabled: The event does not operate and conditions are not evaluated
	Edit or delete event settings
Event Name	User-defined event name - Up to 255 bytes
Condition Type	Type of event trigger condition (elapsed time, error occurrence, pattern only)
Aggregation Basis	Criteria used to aggregate transaction counts
Target Pattern	Include/exclude patterns to which the event applies (URL, status code, etc.)
Trigger Count	Time period and number of occurrences required to trigger the event - The event is triggered when the condition is met the specified number of times within the selected time period
Pause	Temporarily suppresses repeated occurrences of the same event after an alert is sent - Available durations: Disabled, 5 min, 10 min, 15 min, 20 min, 30 min, 1 hr, 2 hr, 3 hr, 6 hr, 12 hr, 1 day - If recovery notifications are enabled, no alert is sent for the same event during the selected time after a RECOVERED notification is received
Event Recipients	Users or groups that receive the event notification (reception tags)

Event Configuration

Transaction events are configured through the steps of event conditions, target patterns, and basic information and notification settings.
With event configuration, you can detect specific transaction patterns and receive alerts.

Add Event

To add a transaction event, go to Event Configuration > Transaction tab, then click the [ + Add Event ] button in the upper-right corner of the screen.

How to Add a Transaction Event
Step 1. Define Event Conditions: Define the criteria that trigger the event.
Step 2. Select Event Target: Select the monitoring targets where the event applies.
Step 3. Basic Information and Notification Settings: Configure the event name, message, and recipients.

Define Event Conditions

Configure the conditions under which a transaction event is triggered.

Condition Type

Select the criteria used to trigger the event.

• Elapsed Time: Transactions that take longer than the specified time (ms).
  • Elapsed Time Threshold: When the condition type is Elapsed Time, enter the value in milliseconds. An event is triggered when a transaction takes longer than the configured time (ms).
• Error Occurred: Transactions in which an error occurs.
• Pattern Only: Transactions that match a specific pattern (such as hitmap patterns).

Aggregation Criteria

Select the unit by which alert conditions are aggregated.

• Aggregation criteria: per agent, per URL of each agent, per error class of each agent, per business of each agent, per URL, per error class, per business, or overall.

Trigger Count (Required)

Configure how many times the condition must be met before a notification is sent.
Example: trigger count 1 sends a notification immediately when the condition is met, while trigger count 3 sends a notification only after the same condition occurs three times consecutively.

Pause

Select a pause duration to prevent excessive alert notifications.

• After an event occurs, the same event will not trigger again during the configured time period.
• Available durations: 1 minute, 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, 2 hours, 3 hours, 6 hours, 12 hours, 1 day

Event Operation Time

Configure the time periods during which the event is active. This allows you to suppress alerts during non-business hours or maintenance windows. If no tag is configured, the event runs continuously for 24 hours while enabled.

1. Click + Add.
2. In Event Operation Time, click + Create New Tag.
3. In Create Event Operation Time Tag, select the tag name, days, time, and color, then click the [ Apply ] button.
4. The created tag appears in the tag list. Select the checkbox to apply it.
5. To edit or delete a tag, click the icon and update or remove it in Edit Event Operation Time Tag.

Caution

When a tag is deleted, it is removed from all alerts where it is applied. However, tags currently in use by event settings cannot be deleted.

Select Event Target

Configure patterns for transaction filtering.

Pattern Configuration

• You can enter multiple patterns, separated by pressing Enter.
• If no pattern is configured, events apply to all transactions in the project.
• Patterns of the same type are applied with an OR condition.
• Patterns of different types are applied with an AND condition.
• You can use wildcards (*) in patterns. Up to two wildcard positions are allowed.
• Each pattern must include at least one character other than the wildcard (*) and slash (/).

Tip

Be careful when combining slashes (/) and wildcards (*)

• /api/*: /api alone does not match. A path must follow /api/ (e.g., ✅ /api/users, ❌ /api)
• /api*: /api itself also matches (e.g., ✅ /api, ✅ /api/users, ✅ /apitest)

Match Patterns

Filter data that matches the specified items. After being applied, match patterns are displayed as blue tags.
You can enter up to 10 patterns for each item.

Item	Description
Operation Name	Operation name pattern
URL	Transaction URL pattern - Example: /api/*, */users/*
Error Class	Error class name pattern - Example: *Exception, *Error
Error Message	Error message content pattern
Status Code	HTTP status code pattern - Example: 4**, 5**

Exclude Patterns

Exclude data that matches the specified items from the filtering targets. After being applied, exclude patterns are displayed as red tags and use the same format as match patterns. You can enter up to 10 patterns for each item.

Pattern Examples

• Exact Match

  Pattern: "hello"
  "hello"     → Match
  "Hello"     → No match (case-sensitive)

• Prefix Match

  Pattern: "hello*"
  "hello"       → Match
  "helloworld"  → Match
  "hi"          → No match

• Suffix Match

  Pattern: "*world"
  "world"       → Match
  "helloworld"  → Match
  "hello"       → No match

• Substring Match

  Pattern: "*ell*"
  "hello"       → Match (h'ell'o)
  "excellent"   → Match (exc'ell'ent)
  "welcome"     → No match (does not contain "ell")

• Composite Patterns

  Pattern: "hello*world"
  "hellobeautifulworld"  → Match
  
  Pattern: "hello*test*"
  "hellomytestcase"      → Match
  
  Pattern: "*test*world"
  "mytestcaseworld"      → Match

Table | Practical Usage Examples

Pattern Type	Examples
URL Patterns	- /api/*: All URLs that start with /api/ - /users/*: All URLs that contain users - /api/v1/users: Only the URL that matches exactly
Error Class Patterns	- Exception: All errors that end with Exception - java.lang.*: All classes that start with java.lang - Timeout*: All errors that contain Timeout
Status Code Patterns	- 4**: All 4xx status codes - 404: Only the 404 status code - 5**: All 5xx status codes

Caution

Pattern Limitations

• Required characters: Each pattern must include at least one character other than the wildcard (*). A pattern cannot consist of wildcards only.
  • ❌ Not allowed: **, *
  • ✅ Allowed: a*, a, a*, /api*
• Empty strings: Empty strings or null values are not matched.
• Consecutive wildcards: Consecutive * characters are treated as a single wildcard.
• Complex patterns: Patterns containing three or more wildcards are not supported.
• No regular expressions: Character classes ([a-z]), quantifiers (+, ?), and grouping (( )) are not supported.
• Case sensitivity: All pattern matching is case-sensitive.
• No escaping: There is no way to escape characters for literal matching.

Basic Information and Notification Settings

Configure the basic information of the event and how notifications are delivered.

Event Activation

Configure whether notifications are sent when an event occurs.

• Enabled: Notifications are sent when the configured conditions are met.

• Disabled: Notifications are not sent even if the configured conditions are met.

Event Name (Required)

Enter the event name to be used as the notification title.

Event Level (Required)

Select the event level (Info, Warning, Critical).

Event Recipients

Specify the members who will receive event notifications.

Receive All

Notifications are sent to all targets (members and channels) with event reception enabled in the project.

Receive by Tag

Notifications are sent to project members who have the selected tag.

1. Select Receive by Tag.
2. In the Receiver Tags section, click [ + Add Tag ] or [ + ].
3. Click + Create New Tag at the bottom of the Event Receiver Tags window.
4. In the Create Tag window, enter a tag name, choose a color, and click [ Create Tag ].
5. To edit or delete a created tag, click the icon in the tag list.
6. In the Event Receiver Tags window, select the desired tag from the Tag List to apply it.

Note

Receiver Tags

Receiver tags are a feature for managing notification recipients (users or channels) at a group level.
When you assign receiver tags to an event, notifications are delivered only to users who have those tags.
If no receiver tag is set, notifications are sent to all users in the project.

---

Reference. Example of Event Behavior

This is an example of an actual transaction event occurrence.

Info

Configuration Conditions

• Aggregation criteria: By agent
• Occurrence count: 2 times
• Silence period: 5 minutes
• URL patterns: /api/posts/**, /delete/*, /*test*/
• Error class patterns: *TimeoutException*, *NullPointerException
• Status code pattern: 4**
• Excluded error class: *IOException
• Excluded status code: 5**

Example of a Triggered Notification Message

The transaction information in the event message displays the values from the most recent transaction that matched the conditions. The event message includes both the configured conditions and the details of the actual transaction that triggered the alert, allowing you to clearly identify which conditions caused the notification.

(ignored count: 3)
[Per Agent] limit: 2, count: 3
[Condition]
url patterns: /api/posts/**, /delete/*, */test/*
error class patterns: *TimeoutException*, *NullPointerException
status patterns: 4**
exclude error class patterns: *IOException
exclude status patterns: 5**
[Transaction]
url: /api/posts/test/timeout
txid: 408093121470636540
status: 408
error class: java.util.concurrent.TimeoutException

Explanation of Event Message Composition

• (ignored count: n): The number of transactions that met the conditions but did not trigger a notification during the silence period. This item is not displayed if there are no ignored transactions during the silence period.
• Aggregation Information: Displayed differently depending on the configured aggregation method.
  • By Agent: [Per Agent] limit: n, count: n
  • By URL: [Per Url] limit: n, followed by a list of each URL and its occurrence count
  • By Error Class: [Per Error Class] limit: n, followed by a list of each error class and its occurrence count
  • By Context: [Per Context] limit: n, followed by a list of each context and its occurrence count
  • By Agent & URL: [Per Agent & Url] limit: n, followed by a list of each URL and its occurrence count
  • By Agent & Error Class: [Per Agent & Error Class] limit: n, followed by a list of each error class and its occurrence count
  • By Agent & Context: [Per Agent & Context] limit: n, followed by a list of each context and its occurrence count
  • Total: [Total] limit: n, count: n
• [Condition]: Displays the conditions that were configured at the time the event was triggered. Only configured patterns are shown.
  • context patterns: Context match patterns
  • url patterns: URL match patterns
  • error class patterns: Error class match patterns
  • error message patterns: Error message match patterns
  • status patterns: Status code match patterns
  • exclude context patterns: Context exclusion patterns
  • exclude url patterns: URL exclusion patterns
  • exclude error class patterns: Error class exclusion patterns
  • exclude error message patterns: Error message exclusion patterns
  • exclude status patterns: Status code exclusion patterns
• [Transaction]: Detailed information about the most recent transaction that met the conditions.
  • url: Transaction URL
  • txid: Unique transaction identifier
  • status: HTTP response status code (not displayed for non-HTTP transactions)
  • error class: Error class (not displayed if no error class exists)
  • error message: Error message (not displayed if no error message exists)

Note

Notes

• Transaction events are aggregated and processed in 1-minute intervals.
• If the condition type is Pattern Only, at least one match or exclusion pattern must be configured.
• Pattern matching is case-sensitive.
• Notification messages include detailed information about the most recent transaction that met the conditions.