Guides and answers for calmer incidents.
Practical writing on running incidents, connecting production systems safely and reviewing what happened, plus the plain-language reference for everything Pindot reads and does.
Blog
From the blog.
Practical writing for the people who run incidents.
Guides
Step by step, for the work itself.
Hands-on guidance on connecting production systems safely and on reviewing incidents well.
- Guide
Asking Pindot good questions: a field guide for on-call engineers
Pindot answers plain language, but some questions get better answers than others. How to name the system and the window, follow up well, read the citations, and hand a finding to the rest of the team.
Using Pindot3 min read
- Guide
A read-only access checklist for connecting production systems
Before any tool reads from production, agree how it gets in, what it can touch and how you will know what it did. A practical checklist, source by source.
Security4 min read
- Guide
Writing a postmortem the review can trust
A postmortem is only as good as the evidence under it. How to build the timeline from records, separate cause from contributing factors, and leave actions that get done.
Incident response4 min read
Glossary
The words of incident work.
The terms of incident management, defined plainly, and where each one touches Pindot.
- MTTRMean time to resolveThe average time from an incident starting, or being detected, to it being resolved. MTTR is also used for mean time to repair, recover or respond, so always say which one you mean.
- RCARoot cause analysisThe process of working out why an incident happened, beyond its immediate trigger, so the underlying problem can be fixed. Most incidents have several contributing causes rather than one.
- Blast radiusHow much is affected when something fails: which services, users, regions or transactions. Reducing blast radius is about containing failures so one fault does not spread.
- Audit trailA chronological record of who did what, when, and with what result, kept so that actions can be reviewed later. A trustworthy audit trail is only ever added to, never edited.
Integrations
What it reads, and where it reports.
Everything Pindot reads from, and where it can send what it finds.
Evaluate
Evaluating Pindot.
Where it runs, how it protects your data, and who it is for.
Deployment options
On-premise, fully air-gapped, or hosted by us, compared side by side.
Read moreSecurity overview
Read-only access, encrypted credentials and a full audit trail, in plain language.
Read moreUse cases by team
What incident managers, on-call, database, change and audit teams each get.
Read more
Questions
Common questions.
The questions buyers ask first, answered plainly.
Stop digging through logs at 2am.
Bring a real incident from your own systems. We will show you how Pindot finds the cause, and where every piece of evidence came from.