Observability
On-Call Burnout Sustainability Calculator
See how your team's on-call load compares to common industry sustainability guidelines.
This is an informational signal based on common industry guidelines, not a diagnosis of your team's specific situation. Use it as a conversation starter, not a verdict.
days
people
Borderline - worth monitoring
1-2 pages/night sustained is a range many teams watch closely.
1.43 pages/night avg
Pages per night (avg)1.43
Nights on-call per person, per rotation7.0
Total pages handled per person, per rotation10.0
Nights on-call per person assumes an even rotation (rotation length ÷ team size). Pages per person per rotation = pages per night × nights on-call. This is a rough signal, not a diagnosis - real sustainability also depends on severity, time of night, and how response is shared.
This is one question. ArchSetu answers it for a whole repository.
Call graph, dead code, blast radius and a health score, in about a minute.
Related tools
All Observability tools →Log Level ReferenceTRACE through FATAL - when to use each level, an example, and production guidance.Alert Threshold CalculatorBaseline mean, std deviation, and a sigma multiplier to a statistically grounded alert threshold.PromQL Rate Query BuilderMetric, labels, range window, aggregation - a syntactically valid rate/irate/increase query.SLO Error Budget CalculatorSLO target, window, and downtime so far - your actual spendable error budget in minutes.Prometheus Alert Rule GeneratorExpression, threshold, and for-duration - a valid Prometheus alerting rule YAML.Log Query Syntax TranslatorThe same filters, translated into Kibana KQL, Datadog, and Splunk SPL syntax side by side.
Was this tool helpful?