# SLO Dashboard * Current SLI ratio over the selected window * Error budget remaining * Good events versus total events * Burn rate trends The dashboard is created automatically when the SLO is created. #### SLO status reference An SLO can appear in these states: * **Healthy**: target is being met and budget is intact * **At Risk**: budget is running low * **Violated**: the SLO has been breached * **Warning**: a slow burn alert is firing * **Degraded**: a fast burn alert is firing * **No Data**: there is not enough metric data to evaluate * **Disabled**: the SLO is administratively disabled #### Best practices **Set the right target** * Start with `99.5%` for internal services * Start with `99.9%` for customer-facing services * Avoid targets above `99.99%` unless your platform can support it * Revisit targets regularly using actual SLI data **Configure alerts well** * Enable both fast and slow burn alerts for production services * Start with the default thresholds * Route fast burn alerts to an on-call channel * Route slow burn alerts to a team channel for review **Choose metrics carefully** * Prefer counter metrics for both good and total events * Make sure the total metric includes all attempts * Prefer service-level metrics over per-instance metrics when possible **Pick a stable time window** * `28d` is the recommended default * `7d` can help during early setup and tuning * avoid windows shorter than `24h` for production SLOs #### Glossary * **SLI**: the measured ratio of good events to total events * **SLO**: the target percentage the SLI must meet over a time window * **Error Budget**: the allowed unreliability, calculated as `100% − SLO Target` * **Error Budget Remaining**: the portion of the budget not yet consumed * **Burn Rate**: how fast the budget is being consumed * **Fast Burn**: alert for sudden high-severity outages * **Slow Burn**: alert for gradual sustained degradation * **Multi-window alert**: alert that checks two windows to reduce false positives * **Time Window**: rolling evaluation period such as `28d` * **Notification Channel**: destination that receives SLO alerts * **PromQL**: Prometheus Query Language used to define SLI metrics and alert queries --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.apica.io/observe/slo/slo-dashboard.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.