To configure alert notifications in ASIATOOLS, you first need to decide what events should trigger a message, choose the delivery channel, and set threshold values that reflect your operational tolerances. The process spans three core areas – defining channels, mapping events, and fine‑tuning alerts – and each step is backed by clear UI controls and optional API parameters.
Below is a practical walkthrough that covers every phase from initial setup to validation, with real‑world numbers, tables, and troubleshooting tips that help you avoid common pitfalls.
1. Overview of the Alert System
ASIATOOLS separates alerts into three layers: Event Sources (metrics, logs, external webhooks), Alert Rules (conditions that evaluate the source data), and Notification Channels (email, SMS, webhook, Slack, Microsoft Teams). When a rule evaluates to true, the platform generates an alert and routes it through the selected channel. Understanding this hierarchy is essential because you can apply different actions to each layer.
2. Prerequisites
- Active ASIATOOLS account with “Admin” or “Alert Manager” role.
- At least one data source already connected (e.g., cloud monitoring, custom API).
- Access to a reachable endpoint for webhook channels (HTTPS recommended).
Before you start, verify that your account role allows alert creation: go to Settings → Users → Roles and check the Alert Management permission box.
Note: If you are on a shared enterprise plan, some channels (e.g., SMS) may require a separate credit purchase. Check the billing console under “Notification Credits” to see your current balance.
3. Step‑by‑Step Configuration
The configuration sequence follows a logical order. Each step is accompanied by a table that shows the required fields and sample values.
3.1 Create a Notification Channel
Navigate to Alerts → Channels → Add Channel. Choose the channel type and fill in the relevant fields.
| Channel Type | Required Fields | Sample Value | Default Timeout |
|---|---|---|---|
| From address, SMTP server, Port, Username, Password, Recipients list | smtp.asiatech.com:587, [email protected], [email protected] | 30 seconds | |
| SMS | Provider (Twilio, Nexmo), API Key, Sender ID, Phone numbers | Twilio, SK‑XXXXXXXX, +1234567890 | 15 seconds |
| Webhook | URL, HTTP method, Headers, Payload template | https://hooks.example.com/alerts, POST, {“alert”:”{{alert_id}}”} | 20 seconds |
| Slack | Workspace, Channel name, Bot token | C01XXXXXXX, #ops-alerts, xoxb‑1234567890 | 25 seconds |
| Microsoft Teams | Tenant ID, Channel webhook URL | abc‑123‑def‑456, https://outlook.office.com/webhook/… | 20 seconds |
After saving, the channel appears in the “Active Channels” list with a health indicator. If the indicator is red, the system reports the last error (e.g., “SMTP authentication failed”).
3.2 Define an Alert Rule
Go to Alerts → Rules → New Rule. The rule builder has three sections: Scope, Condition, and Action.
- Scope: Select the data source(s). You can choose multiple sources if you want a cross‑source rule.
- Cloud Metrics (CPU > 80 % for 5 min)
- Log Errors (count > 10 per minute)
- Custom API (response time > 200 ms)
- Condition: Use the expression builder. You can combine operators (AND, OR) and use thresholds.
- CPU usage > 80 %
- Memory usage > 90 %
- Error count >= 5 in last 2 minutes
- Action: Choose the channel created earlier and specify the template.
- Send email with subject “High CPU on {{host}}”
- Post Slack message with severity “Critical”
Optionally, you can set a Suppress Window (e.g., 5 minutes after the first alert) to prevent duplicate messages. The suppress window can be configured in seconds, minutes, or hours.
3.3 Set Thresholds and Grouping
Threshold tuning is where most teams achieve the balance between sensitivity and noise reduction.
| Metric | Default Threshold | Recommended for Production | Maximum Allowed |
|---|---|---|---|
| CPU Usage | 80 % | 75 % (peak) / 60 % (average) | 95 % |
| Memory Usage | 90 % | 85 % (peak) / 70 % (average) | 98 % |
| Disk I/O | 70 % | 65 % (peak) / 50 % (average) | 85 % |
| Response Time | 300 ms | 250 ms (p95) / 150 ms (p50) | 500 ms |
| Error Rate | 2 % | 1.5 % (p95) / 0.5 % (p50) | 5 % |
Grouping can be applied to reduce alert storms. For example, if you monitor 50 virtual machines, you can group alerts by “Region” so that a single email lists all affected VMs instead of 50 separate messages.
3.4 Enable Escalation and Deduplication
Escalation routes alerts to additional contacts if the initial notification is not acknowledged within a defined period. Deduplication merges identical alerts that arrive within a short time window.
| Feature | Configuration | Typical Value |
|---|---|---|
| Escalation Delay | Time after first notification before escalation | 10 minutes |
| Escalation Level 1 | Primary contact (email, SMS) | [email protected] |
| Escalation Level 2 | Manager (email, Slack) | [email protected] |
| Deduplication Window | Period to consider alerts as duplicates | 5 minutes |
| Deduplication Key | Field(s) used to identify duplicates (e.g., host, metric) | host + metric |
4. Testing and Validation
Before deploying to production, use the built‑in “Send Test Alert” function. This sends a mock alert to the selected channel using the template you defined. The test output includes:
- Delivery status (sent, failed, pending).
- Latency from ASIATOOLS to the channel endpoint.
- Full payload that was transmitted, so you can verify variable substitution.
For webhook channels, you can capture the request with a tool like ngrok or a local HTTP listener to inspect the exact JSON structure.
Tip: Run a load test that simulates the metric threshold being crossed repeatedly. This helps confirm that deduplication and suppression work as expected and that you do not receive a flood of messages.
5. Real‑World Example
Imagine you run a SaaS platform hosted on AWS. You need to be notified when the average CPU utilization of your auto‑scaling group exceeds 70 % for more than 5 minutes, and you want the alert to be posted in the “#infra-alerts” Slack channel, with an email copy to the on‑call engineer.
- Create a Slack channel “#infra-alerts” and obtain a Bot token (scope: chat:write).
- Create an email channel with SMTP credentials for your corporate email service.
- In the rule builder, set the scope to the AWS auto‑scaling group metric namespace.
- Define condition:
AverageCPU > 70 for 5 minutes. - In the action section, add both the Slack channel and the email channel. Use the template:
{ "alert": "High CPU Alert", "host": "{{instance_id}}", "cpu": "{{value}}%", "time": "{{timestamp}}" } - Set suppression to 10 minutes to avoid repeated messages.
After saving, the rule appears with a status “Active”. When CPU hits 71 % for 5 minutes, the system sends a Slack message and an email simultaneously, both containing the instance ID and the exact CPU value.
6. Monitoring and Analytics
ASIATOOLS provides a dashboard under Alerts → Analytics where you can view:
- Alert volume over the last 30 days.
- Mean time to acknowledge (MTTA) per channel.
- False‑positive rate (percentage of alerts that were dismissed without action).
These metrics help you fine‑tune thresholds. For instance, if the false‑positive rate is above 20 %, you may need to increase the threshold or broaden the suppression window.
7. Troubleshooting Common Issues
| Issue | Possible Cause | Resolution |
|---|---|---|
| Alert not delivered (email) | SMTP authentication failure, missing TLS | Verify SMTP credentials in channel settings; ensure TLS 1.2 is enabled. |
| Duplicate alerts despite suppression | Suppression window too short, different rule versions | Increase suppression to at least twice the metric granularity; check for duplicate rules. |
| Webhook returns 401 | Invalid token or missing header | Re‑generate the webhook secret; add Authorization: Bearer <token> header. |
| Slack message missing attachments | Payload exceeds Slack’s 3000 character limit | Trim the payload; use attachments only for critical data. |
| Escalation never triggers | Acknowledgement timeout not reached | Confirm the acknowledgement button is present in the email template; adjust escalation delay. |
When you encounter a problem, start by checking the channel’s health status (green/yellow/red) in the dashboard. If the status is red, the last error message provides a clue. For persistent issues, contact ASIATOOLS support and