Creating Issues
How status page issues are created by Chat and through alerts.
Issues represent active problems affecting your status page components. They can be created automatically by Chat during investigations or linked to alerts.
Agent-created issues
The most common way issues are created is through Chat investigations.
During investigations
When Chat identifies a problem affecting a component, it can
create an issue using the create_status_issue tool. This typically happens
when:
- The assistant detects elevated error rates for a service
- A component is responding slowly or timing out
- A service is completely unavailable
Automatic creation
The assistant creates issues based on its investigation findings. You do not need to explicitly ask for an issue to be created. If the assistant determines there is user-facing impact, it will:
- Identify the affected component
- Assess the severity (degraded or outage)
- Create the issue with a summary
Issue data
Each issue includes the following information:
| Field | Description |
|---|---|
| component | Which status component is affected |
| severity | Either degraded or outage |
| summary | Brief description of the problem |
| startedAt | When the issue began |
Severity levels
- Degraded: The component is functional but experiencing problems (slow responses, intermittent errors)
- Outage: The component is completely unavailable or non-functional
Alert-linked issues
Issues can also be created automatically when alerts are triggered with a component reference.
How it works
When an alert includes a statusComponentId:
- The alert is created with the component reference
- An issue is automatically created for that component
- The issue severity maps from the alert severity
- Both are linked for synchronized resolution
Severity mapping
Alert severity maps to issue severity:
| Alert Severity | Issue Severity |
|---|---|
| Critical | Outage |
| High | Outage |
| Medium | Degraded |
| Low | Degraded |
See Alerts & Status Pages for more details on the linkage.
Best practices
Let the agent lead
The best way to create accurate issues is to let Chat create them during investigations:
- The assistant has full context from log analysis
- Severity is determined based on actual impact
- Issues are linked to the investigation thread
Provide component context
When asking questions, mention the component name if you know it:
"Is there an issue with checkout-service?"
This helps the assistant identify the correct component for any issues it creates.
Trust the impact assessment
The assistant creates issues when it detects user-facing impact. If you are seeing problems but no issue is created, the assistant may have determined the impact is not significant enough to warrant a status page update.
Issues should reflect actual user impact, not every internal error. The assistant uses its investigation findings to determine whether an issue warrants status page visibility.