Triagic docs
Checkups

The curated library

The thirteen checkups shipped with the app, what each one looks at, and which ones need an integration connected first.

The library is grouped into seven categories, and the Checkups page renders one rail per category with your own checkups pinned above them.

CategoryWhat it is for
OptimizeMoney and performance in a system you pay for
ReviewA periodic examination someone has to sign off on
HygieneThings that rot quietly — credentials, stray personal data
Support qualityHow your team is actually serving customers
UnderstandDocumentation exercises: what you have, what your tickets are telling you
ReadinessWhether you could handle the thing that has not happened yet
TriageRun against one named incident rather than on a cadence

Optimize

CheckupWhat it looks atNeeds
Snowflake cost and warehouse efficiencyIdle and oversized warehouses, auto-suspend settings, expensive query patterns, storage nobody meant to keep.Snowflake
DynamoDB capacity and table provisioningOver- and under-provisioned tables, on-demand versus provisioned fit, unused GSIs, tables missing TTL.DynamoDB
Postgres performance and index healthSlow query patterns, missing and unused indexes, table bloat, connection posture.Postgres

Review

CheckupWhat it looks at
SOC 2 readiness reviewA Trust Services Criteria common-criteria walkthrough over your connected systems and Triagic's own access and audit surface, with evidence recorded per control. See Compliance checkups before you run it.
Access reviewWho has access to what, dormant accounts, over-privilege, and shared credentials across Triagic and every connected system.

Hygiene

CheckupWhat it looks at
Credential and integration hygieneCredential age and rotation, stale or failing connections, orphaned servers, integrations nobody uses any more.
PII exposure sweepPersonal data sitting in tickets, chat threads and reachable data stores — where it is, how much, and what should be redacted.

Support quality

CheckupWhat it looks at
SLA and response qualityBreached targets, slow first responses, tickets left to rot, and reply-quality outliers, from your own ticket history.
Knowledge and playbook gapsRecurring ticket clusters no playbook covers — and drafted triage instructions for the largest gaps.

Understand

CheckupWhat it looks at
Environment mapWhat is connected, what the agent can actually see and do with it, where it is used, and what is missing.
Ticket trends and recurring root causesWhat volume is doing, the anatomy of each spike, and the root causes that keep coming back across months.

Readiness

CheckupWhat it looks at
Incident readiness and runbook coverageWhether your playbooks and runbooks cover the incidents you actually have, and what an on-call responder could reach at 3am.

Triage

CheckupWhat it looks at
Webhook and integration failure deep-diveRun this one against a named ticket or incident: trace a webhook or integration failure end to end and find where events are being lost. Give it the ticket in the run's focus.

What you can run on day one

Only three checkups require an integration — Snowflake cost needs Snowflake, DynamoDB provisioning needs DynamoDB, Postgres performance needs Postgres. A card whose required integration is missing offers Connect <provider> instead of Run.

The other ten run with nothing connected at all, because they read Triagic's own data: your members and teams, the audit log, your playbooks, your integration configuration and your ticket history. That is deliberate — a new organization should not meet a wall of locked cards.

A good first run

Environment map. It needs nothing, it produces a document rather than a complaint, and its findings are mostly of the shape here is a system you depend on that Triagic cannot see — which tells you what to connect next.

Where an integration would make a checkup richer rather than possible, the procedure says so and works without it. Connecting more systems generally makes every checkup better, not just the three that insist.

On this page