Hitmap Patterns

Home > Select Project > Alert > Event Configuration > Hitmap pattern tab

Hitmap pattern automatically detects anomalies based on time-based pattern changes in application execution ranges, such as response time distribution and call density.

Without manually configuring complex conditions or thresholds, the system analyzes Hitmaps collected in real time and automatically triggers alert notifications when patterns deviate from normal behavior. Hitmap pattern alerts are especially useful in the following situations.

• When a specific transaction becomes excessively concentrated during certain time periods compared to normal behavior
• When traffic distribution or response patterns differ from the usual baseline
• When pattern-based anomaly detection is required beyond what condition-based rules can capture

Event Configuration

Configure the options for the event patterns to be detected.

Activation

When the toggle is turned on, an alert notification is sent when the corresponding pattern is detected.

• Enabled: An event is triggered when conditions are met.

• Disabled: No event is triggered, and conditions are not evaluated.

Silence

After an event is triggered, the event is suppressed for the selected duration and is not recorded in Event History.

Event Recipient Tags

When recipient tags are configured, notifications are sent to project members who have those tags. If no recipient tag is set, notifications are sent to all users in the project.

1. Click + Add Tag or the + icon.

2. Click + Create New Tag at the bottom of the Event Recipient Tags window.

3. In the Create Tag window, enter a tag name, select a color, and click the [ Create Tag ] button.

4. To edit or delete a created tag, click the icon in the tag list.

5. Select the desired tag from the Tag List in the Event Recipient Tags window to apply it.

Event Active Time

Configure tags to control when events run, such as working hours, non-working hours, or maintenance windows. If no tag is set, events run continuously for 24 hours while they are enabled.

1. Click + Add.

2. Under Event Active Time, click + Create New Tag.

3. In Create Event Active Time Tag, select a Tag Name, Days, Time, and Color, then click the [ Apply ] button.

4. Created tags appear in the tag list and can be applied by selecting the checkbox.

5. To edit or delete a tag, click the icon and modify or remove it in Edit Event Active Time Tag.

Caution

When a tag is deleted, it is removed from all users to whom it is applied. However, tags that are currently in use by event rules cannot be deleted.

Hitmap Pattern Types

When you turn on the toggle for each pattern, an event is triggered when the corresponding pattern is detected.

Hitmap Horizontal Line Pattern

This pattern appears when multiple transactions complete within a similar response time range. Requests cluster around a specific latency band, which indicates increasing service delay or unstable responses from external resources.

• Timeouts or delays occurring in external API, DB, or HTTPS calls
• Requests waiting for a certain duration before being processed all at once
• Repeated latency in shared I/O or network paths

Hitmap Vertical Line Pattern

In this pattern, transactions start at different times but finish simultaneously. Multiple requests are processed at the same moment, which indicates a bottleneck in a shared resource.

• Increased wait time due to shared resources such as DB locks or file locks
• Concurrent processing delays in queues or thread pools
• Temporary request suspension followed by simultaneous resumption due to system pauses such as GC pauses

Tip

A Hitmap vertical line pattern is a signal that lock contention or bottleneck resources should be inspected.

Hitmap Flying Pattern

This pattern appears when response times rise and fall in waves at regular intervals due to shortages in shared resources such as specific system components or logs.

• Shortages in shared resources such as GC, connection pools, or file handles
• Periodic latency factors such as log flushing or storage I/O
• Batch jobs or background jobs that periodically consume resources

Tip

A Hitmap flying pattern strongly indicates periodic bottlenecks or resource shortages.

Hitmap Overload Pattern

This pattern occurs when transactions become abnormally concentrated within a specific response time range. It appears when requests fail to distribute normally and instead pile up in a narrow band due to temporary load spikes or early signs of failure.

• Transactions accumulate in a queue due to temporary failures or delays and are then processed in bulk
• Backend service response latency
• Insufficient processing capacity caused by traffic concentration during specific time periods

Tip

An overload pattern indicates temporary service quality degradation or load balancing failure.

Hitmap Flood Pattern

This pattern indicates an overall increase in response times caused by excessive requests or load. It reflects a broad performance degradation across the service.

• Sudden spikes in user traffic or automated traffic
• System resource shortages such as CPU, memory, or GC pressure
• Overall response quality degradation due to backend bottlenecks

Tip

A flood pattern requires immediate investigation.