Knowledge Hub
This library is for engineers who need to reconstruct what changed, what failed, and what evidence supports a production-incident hypothesis. It favours traceable inputs over generic root-cause claims.
Start here
- Incident correlation for production investigations
- How to correlate deployments and incidents
- How to debug a CI pipeline without guessing
Delivery and infrastructure evidence
- CI/CD monitoring that preserves release evidence
- Kubernetes deployment monitoring for incident investigation
- OctoLaunch vs Datadog for deployment investigations
How to use this material
Use the guides to define a fixed incident boundary, compare competing causes against the same evidence, and preserve source links for later review. Do not treat a correlation as proof of causation or run destructive production commands from a generic article.
For product scope and supported integration categories, see the product overview and integrations. For a broader entry point, visit the Knowledge Hub overview.