Best practices

These guides help you wire Incido into a reliable operating model: automated signals from monitoring, safe programmatic creates through the API, and a clear split between what your organization tracks as affected services and how each status page presents them to different audiences.

Read Integrations and automation when you connect Pingdom, Grafana, or other tools—the page leads with monitors and correlation groups—or when external systems create incidents and maintenances over the API. Read Components and status pages when you design your service catalog and decide how customers (and internal viewers) should see health and structure on each page.

Together with Components and taxonomies, Monitors and correlation groups, and Status pages, these articles explain recommended patterns—not the only valid setup, but approaches that stay predictable when alerts are noisy or integrations retry requests.

Troubleshooting

You are unsure which article to open. Start with Integrations and automation if the problem involves webhooks, the API, or duplicate records. Start with Components and status pages if the problem is layout, naming on one page versus another, or why an incident does not appear on a specific status page (often publication rules plus component overlap—see Status pages).