Skip to main content

Attach your first alert

Once the WhaTap agent is installed, the next thing to do is make sure you know the moment something goes wrong. This guide walks you through setting up your first alert and verifying delivery in 5 minutes.

This guide is for project administrators who have just finished installing the agent.

What you get from this guide
  • Automatic Slack/Email notifications when a metric crosses its threshold
  • A system where the team catches incidents through alerts, not by refreshing a dashboard

Prerequisites​

  • The WhaTap agent is installed and connected to the project in Active state
  • Project admin permission
  • A Slack channel webhook URL or a recipient email address

Step 1. Register an alert channel​

First, register where WhaTap will send alerts (Slack, Email, etc.).

  1. From the left menu, select Alert > Event reception settings.
  2. Click the Add button, then select Slack or Email.
  3. Enter the recipient:
    • Slack: the channel's Incoming Webhook URL
    • Email: the recipient email address
  4. Click the Save button.
Tip

Slack Webhook URLs are issued per channel from the Slack app's Incoming Webhooks feature. Create a dedicated team channel as an inbox to reduce noise.

Step 2. Create your first event rule​

Start from the most basic: an alert when CPU usage crosses a threshold.

  1. Select Alert > Event settings.
  2. Click the Add metric event button.
  3. Enter the following:
    • Event name field: CPU usage threshold exceeded
    • Target agent dropdown: all agents in the project or a specific agent
    • Metric dropdown: cpu_usage (or system_cpu)
    • Condition field: value exceeds 80
    • Duration field: 1 minute (to exclude short spikes)
    • Alert level dropdown: Warning
  4. In the Alert channel field, select the Slack/Email you registered in Step 1.
  5. Click the Save button.

Step 3. Verify delivery with a test message​

Confirm the rule actually works by sending a test.

  1. Click the Send test button on the event rule you just created.
  2. Check that the test message from WhaTap arrives in the registered Slack channel or email.
If the alert doesn't arrive
  • Recheck the Slack Webhook URL for typos
  • Check corporate email filtering / spam folder
  • Verify the receiving channel is enabled

Verify​

  • A WhaTap test message arrived in the registered channel
  • The CPU usage threshold exceeded rule is shown as Enabled in Alert > Event settings
  • The test delivery appears in Event history

Congratulations — your first alert is connected. From now on, the team channel will receive an automatic notification the moment CPU crosses 80%.

Next steps​

Last updated on