---
Title: Monitor alerts
URL Source: https://company-skill.com/p/eb/eb-monitor-alerts
Language: en
Description: You want to consume monitoring events from Alibaba Cloud services (like RDS, DNS, or Anti-DDoS) and either process them programmatically or visualize them with alerts. This includes setting…
---

# Monitor alerts

Part of **EventBridge**. Route queries via `POST https://company-skill.com/api/route`.

## What You Want to Do

You want to consume monitoring events from Alibaba Cloud services (like RDS, DNS, or Anti-DDoS) and either process them programmatically or visualize them with alerts. This includes setting thresholds, exporting data, or building dashboards.

**Typical User Questions**:
- RDS Anti-DDoS 
- How to create a monitoring dashboard?
- Can I export monitoring data in real time?

## Decision Tree

Pick the best path for your situation:

- **If** you need to route raw monitoring events (e.g., from RDS or WAF) to custom code or external HTTP endpoints → Use API (go to *eb/eb-monitoring*)
- **If** you want to build a visual dashboard with drag-and-drop panels or configure email-based alert subscriptions → Use (go to *eb/eb-monitoring*)
- **If** your use case requires handling event payloads larger than 10KB or exceeds **100 QPS** → Neither path fully supports this; consider batching or throttling
- **Otherwise (default)** → Start with **** if you prioritize UI-based setup and email alerts; choose ** API ** if you’re building automated pipelines

## Path Comparison

| Path | Best For | Complexity | Code Required | Automation | Key Fact | Detail Skill |
|------|----------|------------|---------------|------------|----------|-------------|
| API | RDSDNSAnti-DDoS | medium | Yes | Yes | Events delivered in CloudEvents 1.0 format; subject to **100 QPS** rate limit | `eb/api/eb-monitoring` |
| Console / Dashboard | medium | No | No | Uses **Hybrid Cloud Monitoring** integration; requires **metric repository** setup | `eb/guide/eb-monitoring` |

## Path Details

### Path 1: API 

**Best For**: RDSDNSAnti-DDoS 

**Brief Description**: EventBridge API allows direct consumption of raw monitoring events from cloud services like RDS, DNS, and Anti-DDoS in CloudEvents 1.0 format via synchronous event delivery. It enforces **event type constraints** and delivers events to your application endpoint without UI interaction.

**Key technical facts**:
- Billing: Pay-per-use with free tier (1000 events/month for most services); billed per successfully delivered event
- Regions available: cn-hangzhou, cn-shanghai, cn-beijing

**When to Use**:
- Need programmatic access to raw monitoring events from services like RDS, DNS, or WAF
- Building automated event processing pipelines requiring code-level control
- Integrating with external systems via HTTP endpoints or custom functions

**When NOT to Use**:
- Prefer visual dashboard creation without coding
- Require enterprise alert configuration through UI forms
- Need subscription-based email notifications for monitoring data

**Known Limitations**:
- Requires handling raw JSON event payloads with service-specific schemas
- Rate limited to **100 QPS** per account for most services
- Event size limited to 8KB-10KB maximum per event
- Authentication required for publishing events but not receiving them

### Path 2: Console / Dashboard
**Brief Description**: EventBridge console provides UI-driven workflows to create enterprise monitoring dashboards, configure alert rules with thresholds, and set up real-time data export through **Hybrid Cloud Monitoring** integration. Key actions include **View Enterprise Monitoring Dashboard**, **Add Metric**, toggle the **Subscribe switch**, and use the **New Alert Rule panel** to **Set Alert Rule**.

**Key technical facts**:
- Billing: Alert rules billed per request (0.001/event stream alert); 1000 free requests/month
- Prerequisites: EventBridge activated and authorized, Custom event bus or stream created, **Hybrid Cloud Monitoring** enabled, **metric repository** created

**When to Use**:
- Need visual dashboard creation with drag-and-drop panel configuration
- Require email subscription for monitoring reports with scheduled delivery
- Prefer form-based alert configuration with mute periods and contact groups

**When NOT to Use**:
- Need programmatic event consumption in application code
- Require handling raw CloudEvents payloads directly
- Building CI/CD automation for monitoring setup

**Known Limitations**:
- Gmail cannot display dashboard chart images correctly (requires alternative email provider)
- Default **metric repository** includes ECS metrics that must be manually removed before adding EventBridge
- Alert rule evaluation limited to **100 QPS** quota
- Requires navigating through multiple console pages (EventBridge → CloudMonitor)

## FAQ

Q: Which path should I start with?
A: If you’re an operations engineer needing email alerts and dashboards, start with the console path. If you’re a developer building event-driven microservices, start with the API path.

Q: What if I need to process 150 events per second but chose the API path?
A: You’ll hit the **100 QPS** rate limit and experience dropped events unless you implement client-side throttling or request a quota increase.

Q: What if I used the console path but my team uses Gmail for alerts?
A: Dashboard chart images in email alerts won’t render correctly in Gmail — you’ll need to switch to another email provider or embed links instead of images.

Q: Can I use the API path to create a dashboard like the console offers?
A: Not directly — you’d need to build your own frontend and store/process events, whereas the console provides **View Enterprise Monitoring Dashboard** out of the box.

Q: Why do I need to clean the default metric repository when using the console path?
A: The system preloads ECS metrics into the **metric repository**, which can interfere with EventBridge metric ingestion unless manually removed before you **Add Metric**.

Q: Does the API path support authentication for receiving events?
A: No — authentication (via `Authorization: Bearer $EVENTBRIDGE_API_KEY`) is only required for *publishing* events, not receiving them.

Q: What happens if my event payload is 12KB and I use the API path?
A: The event will be rejected — the API enforces a hard limit of 8KB–10KB per event due to **event type constraints**.

## Related queries

monitor events, set up alerts, monitoring dashboard, alert rules, real-time data export, event stream monitoring, cloud service events, RDS monitoring, Anti-DDoS alerts, ActionTrail logs, DNS event monitoring, how to monitor events, can I export monitoring data, configure alert rules, create monitor

---
Part of [EventBridge](https://company-skill.com/p/eb.md) · https://company-skill.com/llms.txt