Server / Process

Home > Select Project > Alert > Event Settings classic

WhaTap Monitoring detects a wide range of anomalies that occur across servers and processes, and delivers alerts accordingly. When you configure event rules, you can receive alerts at either the Warning or Critical level whenever specified conditions are met.

Default Options

You can define event conditions based on servers and processes.

• Search: Search for specific events by selecting an event name or an event recipient tag.
• + Add Event Rule: Add a new event rule.

Table | Server and Process Event Settings Layout

Item	Description
Condition	Server metrics and threshold conditions used for event detection - Example: networkKbps >150,000,000, diskIo ≥90
Server / Process	The server or process to which the event condition applies
Event Recipient Tag	User groups that will receive notifications
	Edit a saved event
	Copy the event configuration to the current or another project

Server list selection window

This is the layout of the Server list window where you choose the target server when creating an event rule. Status, time, version, and OID columns are provided together so that you can distinguish rows that have the same server name, IP, and OS but a different agent.

Table | Columns of the server list selection window

Item	Description
Server Name	Server name. Stays fixed on the left along with the checkbox even when you scroll horizontally
IP	IP address of the server
OS	Operating system type
Status	Shows whether the agent is active, as a badge
Inactive time	The time the collection server determined the agent to be inactive. Shows - when there is no value
Agent version	Installed agent version
OID	Unique number that identifies the agent. The final criterion when all of the above are identical

The list is sorted with currently active agents at the top. You can change the sort criterion by clicking each column header, and Inactive time is sorted by time rather than as text.

Note

When the same server appears on multiple rows

If you reinstall an agent, multiple rows with the same server name, IP, and OS can remain. In that case, check Status and Inactive time first to choose the agent currently in use. If those two values are also the same, distinguish them by OID.

This selection window appears with the same layout in the process event rule window and in the inspection registration and edit windows.

Event Configuration

The Event Configuration screen consists of three tabs. Each tab groups related events for easier review.

• All: View all event rules configured for servers and processes at once.
• Server: View and manage server event rules only.
• Process: View and manage process event rules only.

Add Event Rules

Server

Add Server Event Rules

Configure event rules based on metrics collected from servers.

Note

You can assign only one event to a single server.

1. Go to Alert > Event Configuration classic.

2. Click the [ + Add Event Rule ] button.

3. Enter an event name (up to 100 characters) in Title.

4. Select Server as the Event Type.

5. Select the server to which the rule will apply from the Server List.

6. Configure the Event Trigger Conditions.

   • Metrics

   Metric	Description
   Restart	Alert triggered when the server restarts
   No Data	Agent No Data alert triggered when normal data is not received from the agent for a specified duration
   Port	Alert triggered when the listening port of a network daemon becomes inactive - To use port check events, you must enable monitoring for specific IPs and ports in agent settings - For details, see TCP Port Monitoring Alerts
   Network IOPS	Packet-per-second threshold per network interface card (input + output) - To exclude specific devices from alerts, enable or disable them via Server List > Server Details > Network Details
   Network BPS	Bits-per-second threshold per network device (input + output) - To exclude specific devices from alerts, enable or disable them via Server List > Server Details > Network Details
   Disk I/O	Disk I/O usage rate (%) per disk - Values may be inaccurate for parallel-processing disks such as SSDs or RAID
   Disk Usage	Percentage of used disk capacity
   inode	inode usage percentage per file system - Requires agent version 1.2.0 or later
   CPU	CPU usage percentage
   Memory	Memory usage percentage
   Steal	Event based on CPU steal time percentage
   Swap	Swap memory usage percentage

   • Condition: An event is triggered when the configured threshold is exceeded. If multiple levels are met at the same time, events for all applicable levels are triggered.

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

   • Duration: If the condition persists for the configured duration, the state is evaluated as Warning or Critical and a notification is sent.

   • Enable: Enable the toggle to activate alert notifications.

7. Click the [ + Add Tag ] button under Event Recipient Tags.

   a. Select recipients for alert notifications from the tag list.

   b. You can also add a new tag by selecting + Create New Tag.

   Note

   When configuring events, selecting event recipient tags allows notifications to be sent to project members and third-party plugins associated with those tags. You can assign tags to project members and third-party plugins separately in the Event Notification Settings menu.

8. Once server event configuration is complete, click [ Save ].

Process

Add Process Event Rules

Configure events based on changes in process count, CPU usage, or memory usage for specific processes.

1. Go to Alert > Event Configuration classic.

2. Click the [ + Add Event Rule ] button.

3. Enter an event name (up to 100 characters) in Title.

4. Select Process as the Event Type.

5. Under Server List in Event Trigger Conditions, click [ No agent selected ].

   a. Select servers in the Server List window and click [ Apply ].

   b. When the Project Default Policy toggle is enabled, the default alert policy is applied to servers managed by the project.

6. Select a process or process group in the Process selection window.

   Note

   For instructions on adding process groups, see this document.

7. Select the process owner.

   • If no owner is specified, the rule applies to all processes with the same name regardless of owner.

   • Even if the owner is omitted, event conditions operate on an owner-process basis.

8. Configure Metrics, Conditions, Levels, Duration, and Enablement.

   • Metrics

   Metric	Description
   Process Count	Event based on the number of processes with the same name - Specify counts for Critical and Warning
   Process CPU	Process CPU usage percentage
   Process Memory	Process memory usage percentage

   • Condition: Set thresholds for Process CPU and Process Memory. Alerts are triggered when thresholds are exceeded, with Critical taking precedence.

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

   • Duration: If the condition persists for the configured duration, the state is evaluated as Warning or Critical and a notification is sent.

   • Enable: Enable the toggle to activate alert notifications.

9. Click the [ + Add Tag ] button under Event Recipient Tags.

   a. Select recipients for alert notifications from the tag list.

   b. You can also add a new tag by selecting + Create New Tag.

   Note

   When configuring events, selecting event recipient tags allows notifications to be sent to project members and third-party plugins associated with those tags. You can assign tags to project members and third-party plugins separately in the Event Notification Settings menu.

10. Once process event configuration is complete, click [ Save ].

    • If alert conditions are configured incorrectly, disable the alert or reconfigure the conditions.

    • If the Process or Process Owner is set incorrectly, disable the alert to resolve any ongoing notifications, then reconfigure the alert conditions.

Edit Event

1. Go to Alert > Event Configuration classic.

2. Click the icon for the event you want to edit.

3. Modify the event in the Add Event Rule window.

4. Click the [ Save ] button.

   • After the update, new alerts are triggered when incoming data meets the updated conditions.

   • If changes are made to specific metrics during event editing, any ongoing events triggered by those metrics are changed to a canceled state.

   • For process alerts, if one or more of the following values are modified: Title, Process, or Process Owner, any ongoing events triggered by those conditions are changed to a canceled state.

Delete Event

1. Go to Alert > Event Configuration classic.

2. Click the icon for the event you want to delete.

3. In the Add Event Rule window, click the [ Delete ] button in the upper right corner.

Copy Event

Copy an alert policy to a selected project.

1. Go to Alert > Event Configuration classic.

2. Click the icon for the event you want to copy.

3. When the Copy Event Configuration window appears, select a Project or choose Copy to Current Project.

4. After selecting the target project, click the [ Copy ] button.

   • When copying events multiple times within the same project, a new event is created for each copy.

   • Copied event names include the suffix (copy).

   • Example: Original event name Default → Copied event name Default(copy)