Send Monitor Events to AI Team Channels
3 minute read
Overview
You can send monitor events directly to an AI Team channel. When the monitor fires, it creates a new thread in the channel, allowing your team and AI teammates to collaboratively investigate the issue.
Channels provide a shared workspace where specialists, custom teammates, and humans can analyze alerts together. Thread history, summaries, and resolutions remain searchable for future audits.
How threads begin in channels
Threads in AI Team channels can be initiated through:
- Direct chat: Team members start a thread to ask a question or share an update
- Monitor events: Monitors post alerts directly to channels (described in this guide)
- Workflow triggers: Workflows can post messages to channels as part of automated processes
For complex automation scenarios involving conditional logic, data transformation, or multi-step responses, use a workflow instead of posting directly to a channel.
Configure the monitor
To send monitor events to a channel:
- Open an existing monitor or create a new one
- In the Notifications section, type
@to open autocomplete - Select the channel from the list (channels appear with a
#prefix) - Save the monitor
When the monitor changes state, it creates a new thread in the channel with the alert details.
Conditional channel notifications
Use conditional formatting to post to channels only for specific monitor states:
Post on alert only
{{#is_alert}}
@channel-alerts
{{/is_alert}}
Post to different channels by severity
{{#is_alert}}
@channel-critical-alerts
{{/is_alert}}
{{#is_warning}}
@channel-warnings
{{/is_warning}}
Route by service
{{#is_alert}}
{{#is_exact_match "service.name" "payment-api,checkout-api"}}
@channel-payments-ops
{{/is_exact_match}}
{{^is_exact_match "service.name" "payment-api,checkout-api"}}
@channel-alerts
{{/is_exact_match}}
{{/is_alert}}
What happens when a monitor posts to a channel
When a monitor fires and posts to a channel:
- A new thread is created with the alert details
- OnCall AI evaluates the context and assigns appropriate teammates
- Teammates collaborate in the thread, sharing analysis and recommendations
- The thread remains open for human review and additional investigation
- Mark the thread as resolved once the issue is addressed
The thread includes:
- Monitor name and alert summary
- Evaluated metric values and thresholds
- Group-by attributes (service name, namespace, etc.)
- Links to relevant dashboards and metrics
Combining channels with other notifications
You can post to channels alongside other notification recipients:
{{#is_alert}}
Alert detected for {{service.name}} in {{ed.tag}}
@channel-alerts
@slack-ops-channel
@oncall@team.com
{{/is_alert}}
This configuration posts to the AI Team channel for collaborative investigation while also sending notifications to external Slack channels and email.
Channels vs workflows
Choose the right approach based on your needs:
| Use case | Channel | Workflow |
|---|---|---|
| Simple alert routing with AI triage | ✅ | |
| Collaborative human + AI investigation | ✅ | |
| Conditional logic and branching | ✅ | |
| Data transformation before notification | ✅ | |
| Multi-step automated responses | ✅ | |
| Posting to external systems (Slack, email) | ✅ |
For automated processing that requires logic, use a workflow. For collaborative investigation where humans and AI teammates work together, post directly to a channel.
Related resources
- Channels and Direct Messages - Learn about AI Team channels
- Trigger AI Team Workflows - Automate responses with workflows
- Monitor Notifications - Configure notification recipients and formatting
- AI Team Overview - Understand the AI Team ecosystem