Skip to main content
Incidents are how you communicate ongoing issues to your users. When something goes wrong with your services, create an incident to keep users informed.

​
Incident Lifecycle

Incidents progress through these statuses:
StatusDescription
InvestigatingYou’re aware of an issue and looking into it
IdentifiedYou’ve found the root cause
MonitoringA fix has been applied and you’re monitoring
ResolvedThe issue is fully resolved

​
Creating an Incident

  1. Go to Dashboard > Incidents
  2. Click Create Incident
  3. Fill in the title, severity, and affected services
  4. Add an initial update message
  5. Click Create

​
Severity Levels

Choose the appropriate severity based on impact:
SeverityUse When
MinorSmall number of users affected, workarounds available
MajorSignificant impact, core functionality degraded
CriticalComplete outage, all users affected

​
Posting Updates

Keep users informed by posting updates as the situation evolves: 
kodo incidents update inc_abc123 \
  --status identified \
  --message "We've identified a misconfigured database connection pool"

​
Best Practices

Users appreciate honesty. If you don’t know the cause yet, say so.
Even if there’s no new information, post updates every 30-60 minutes during active incidents.
Only provide time estimates if you’re confident. “We expect to have more information within the hour” is better than a specific time you might miss.
After major incidents, consider adding a final update explaining what happened and what you’re doing to prevent it.

​
Auto-Created Incidents

Kodo can automatically create incidents when monitors detect failures. Auto-created incidents have source tracking (visible as badges in the dashboard) and pass through a safeguard pipeline including flap protection, cooldowns, and dedup. You can configure auto-created incidents to start as drafts (hidden from the public status page until you review them) or to publish immediately.

Incident Safeguards

Learn about flap protection, draft mode, cooldowns, notification batching, and other safeguards that prevent false incidents.

​
Incident Sources

SourceBadgeMeaning
Manual—Created by a team member
APIAPICreated via the REST API
Auto: UptimeAuto: UptimeHTTP monitor detected failures
Auto: HeartbeatAuto: HeartbeatHeartbeat monitor timed out
Auto: IntegrationAuto: IntegrationThird-party integration degraded
Auto: BeaconAuto: BeaconClient error rate exceeded threshold

​
Draft Incidents

When your organization has draft mode enabled (Settings > Automation):
  • Auto-created incidents show a Draft badge in the dashboard
  • They are not visible on the public status page
  • Click Publish to make them public, or wait for auto-publish if configured

​
Notifications

When you create or update an incident, subscribers are automatically notified based on your notification settings. Auto-created incidents respect your notification batching settings.