Triagic + PagerDuty: ticket investigations over your logs, errors and metrics, read-only
Read incidents, on-call schedules, and escalation policies. Write tools stay disabled. Triagic connects to PagerDuty from the desktop app on each member's machine, with a credential you configure, and shows every call it makes while it investigates a ticket. Nothing is copied out of PagerDuty.
What you can ask
- Check PagerDuty for errors from the checkout service in the last hour and group them by message
- In PagerDuty, did latency for the import worker change after the 16:02 deploy?
- Find every PagerDuty event that mentions request id 7f3a-…-c2 and put them in order
- Is the alert in PagerDuty for the export queue still firing, and since when?
- What did PagerDuty record for the pod that restarted at 11:31?
What the agent can do
Triagic exposes every tool the PagerDuty server annotates as read-only, and nothing else. Write tools only exist when the server is started with a flag this catalog never passes.
Connect in three steps
- 1
Mint a read-only credential in PagerDuty
Create a dedicated user or token that can only read. Write tools only exist when the server is started with a flag this catalog never passes.
- 2
Add it in the Triagic portal
Integrations, then Add shared data source, then PagerDuty.
- User API token: PagerDuty → User Settings → API Access → Create API User Token. It must be a user token: the server calls /users/me at startup to work out whose name to act under, and an account-level REST key has no user behind it. That call failing is not reported: the server starts anyway and then cannot answer anything about the current user. Not an Events API integration key either.
- 3
Let a desktop pick it up
Saving validates the shape of what you typed. The first desktop app to sync starts PagerDuty locally and reports running or degraded with the error text.
Field-by-field setup, TLS options and the error table: PagerDuty in the docs.
Read-only, by construction
Write tools only exist when the server is started with a flag this catalog never passes.
FAQ
- Can Triagic change anything in PagerDuty?
- No. Write tools only exist when the server is started with a flag this catalog never passes. Give it a read-only credential as well, so the guarantee does not rest on one layer.
- What do I need to connect PagerDuty?
- User API token. The desktop app on a member's machine starts the connection; the portal never holds a live process.
- Does PagerDuty cost extra?
- No. Every connector is included in the seat price. Start a 14-day trial without a card.
Related integrations
Try it on your own PagerDuty
No card. Install the desktop app, connect PagerDuty read-only, and triage a real ticket this afternoon.