text stringlengths 0 59.1k |
|---|
- Exposes an HTTP interface using Hono at `http://localhost:3141`. |
- Attaches the `observability` instance so trace data persists without extra wiring. |
### Running the Agent |
Once deployed, the agent handles natural conversations for incoming requests. |
 |
I watch the coordinator delegate work in three steps: |
1. `TranscriptFetcher` calls the MCP tool to retrieve the English transcript. |
2. `BlogWriter` receives the transcript and formats a structured Markdown article. |
3. The supervisor returns the Markdown output without extra commentary. |
VoltOps captures each delegation, tool call, and LLM response, so I can inspect the chain step by step. |
Prompt example: |
``` |
Extract the transcript of this video: https://www.youtube.com/watch?v=U6s2pdxebSo and write a blog post in English. |
``` |
### Next Steps |
Here are the next improvements on my list: |
1. Integrate additional MCP providers (for example, keyword research or SEO scoring) before handing the transcript to the writer. |
2. Add guardrail agents that fact-check statistics or detect sensitive topics before publication. |
3. Persist finished articles to a CMS via webhooks or a platform-specific API. |
4. Allow the coordinator to branch into multiple writing styles (technical deep dive, social recap, executive summary) based on user preferences. |
5. Introduce human-in-the-loop review stages using VoltAgent workflows and the VoltOps timeline UI. |
<|endoftext|> |
# source: VoltAgent__voltagent/website/observability/alerts.md type: docs |
--- |
title: Alerts |
--- |
# Alerts |
<video controls loop muted playsInline style={{width: '100%', height: 'auto'}}> |
<source src="https://cdn.voltagent.dev/docs/voltop-docs/alert.mp4" type="video/mp4" /> |
Your browser does not support the video tag. |
</video> |
<br/> |
<br/> |
Alerts notify your team when AI agent metrics exceed defined thresholds. VoltOps evaluates alert conditions every minute and triggers notifications through configured channels. |
## Alert Components |
An alert consists of: |
- **Metric**: What to monitor (error rate, latency) |
- **Condition**: Threshold and condition type (count or percent) |
- **Time Window**: Evaluation period (5, 15, 30, or 60 minutes) |
- **Filters**: Scope the alert to specific traces |
- **Channels**: Where to send notifications (webhook, Slack) |
- **Cooldown**: Minimum time between notifications |
## Creating an Alert |
Navigate to the Alerts page in VoltOps and click "Create Alert". |
### Selecting a Metric |
| Metric | Description | |
| ------------ | ------------------------------------------------------- | |
| Errored Runs | Counts traces with `status: error` or `error_count > 0` | |
| Latency | Calculates average trace duration in the time window | |
### Condition Types |
For error rate alerts: |
- **Count**: Trigger when error count exceeds N runs |
- **Percent**: Trigger when error percentage exceeds N% |
For latency alerts: |
- Trigger when average latency exceeds N seconds |
### Time Windows |
Available windows: 5, 15, 30, or 60 minutes. The alert evaluates all traces within this rolling window. |
### Cooldown Period |
After an alert triggers, VoltOps waits for the cooldown period before sending another notification. Available options: 5, 15, 30, 60, or 120 minutes. |
## Filters |
Filters narrow the scope of an alert to specific traces. Multiple filters are combined with AND logic. |
### Available Filter Fields |
| Field | Type | Operators | Description | |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.