PagerDuty · Connector
How do we connect PagerDuty to AI agents on our own infrastructure?
Katonic connects to PagerDuty, reads incidents and indexes them in the Knowledge Engine on infrastructure you control. An agent can then find past incidents like the one in front of it, with a model you serve, so your operational history is not sent to a public AI service.
What it reads.
From PagerDuty.
- 01Incidents
- 02Only the services you name, where you list them
Through: PagerDuty REST API v2
Where the content goes
Into a knowledge store you run.Content is pulled into the Knowledge Engine on infrastructure you own or control, and indexed there. Agents answer from it with a model you serve. The documents, the index and the questions are not sent to a public AI service.
How it signs in
OAuth 2.0.
Permissions
Access is set on the source in Katonic: everyone given access to the source can retrieve its documents. The permissions PagerDuty holds for each item are not read.
Sync
Incremental, by the time of the incident.
You set how often the source is read again, in minutes, hours, days or weeks.
Use case pages that name PagerDuty.
Does it change incidents in PagerDuty?
No. The connector reads incidents into the Knowledge Engine.
Can we limit it to some services?
Yes. You list the services to read.
Where are the incidents indexed?
In the Knowledge Engine, on infrastructure you own or control. They are not sent to a public AI service.