Concepts
Environments & tone
A prod outage should read like war. A staging hiccup should read like a heads-up. Inkvo maps each environment to a tone so the urgency of the words matches the urgency of reality.
The mapping
| Environment | Tone | Default routing |
|---|---|---|
| production | Urgent | Page on-call immediately |
| staging | Informational | Post to channel, no page |
| development | Debug | Quiet — visible in-app only |
Tone changes the writing, the severity thresholds, and the default routing — all at once. You're not configuring three separate alerting policies; you're declaring what an environment means.
Setting the environment
Inkvo reads the OTel deployment.environment resource attribute. Anything that isn't production or staging is treated as development by default; you can remap custom names (preview, canary) in Settings → Detection.
Unset environment = development
If the attribute is missing, Inkvo assumes development and stays quiet. A prod service with no environment tag won't page you — always set it explicitly.