AI assistant for PagerDuty
Connect PagerDuty so Joshu can check on-call schedules, review incident histories, and summarize infrastructure alerts for your team.
Then $95 a month with no token fees, no resets, and no caps.
What you can ask Joshu in PagerDuty
You: What high-urgency incidents triggered in PagerDuty during the weekend?
Joshu reviews the incident log, summarizes alerts by affected service and resolution duration, and leaves a brief on your desk.
You: Who is currently on call for the primary infrastructure escalation policy?
Joshu checks the on-call schedule, identifies the active primary and secondary engineers, and notes the next rotation shift.
You: Draft a post-incident timeline from yesterday's database outage alert.
Joshu pulls trigger timestamps, responder acknowledgments, and resolution notes, structuring a clean retrospective draft.
Incident queues, escalation policies, and on-call schedules in PagerDuty connect directly to your daily engineering oversight.
What Joshu does
Joshu keeps track of your PagerDuty services to monitor operational health, verify who is on call, and summarize overnight incident activity. When production alerts occur, Joshu links alert payloads to recent deployments, tracks the duration to acknowledgment, and drafts post-mortem timelines ready for engineering review.
What you do
Connect your PagerDuty account using OAuth and select which services or teams Joshu should monitor. Choose whether incident summaries appear in your morning executive brief or come as a message when Joshu's scheduled check finds a critical incident. Joshu asks you to approve each incident update or note before it goes out.
Why it sticks
Incident reviews often stall because gathering alert logs, paging timestamps, and responder actions across tools requires tedious manual assembly. Joshu compiles the entire incident timeline automatically so post-mortems can happen without friction.
Permissions and limits
Joshu accesses PagerDuty using official OAuth scopes. It reads incident histories, on-call schedules, and service configurations according to authorized roles. It cannot snooze or resolve incidents or change escalation policies without explicit confirmation.
Frequently asked questions
Joshu connects to PagerDuty through OAuth and accesses the services, escalation policies, and incident queues you authorize. It tracks on-call schedules, summarizes incident alerts, drafts retrospective timelines, and ties production alerts back to your engineering tickets and morning calendar briefs. You work with an assistant who has a desk, a computer, and persistent memory, not another alert dashboard to refresh during quiet periods.
Yes. Every Joshu runs in its own isolated, sandboxed cloud computer. Incident logs, responder notes, and alert payloads Joshu reads stay in that private sandbox. Joshu only accesses services you authorize, and your data is never used to train public AI models.
No. Acknowledging, resolving, reassigning, or snoozing an incident waits for your approval, and so do incident notes, status updates, schedule overrides, and escalation policy changes. Joshu reads incidents, schedules, and on-call lists and drafts timelines on its own.
Only the PagerDuty accounts, services, and escalation policies authorized during OAuth sign-in. Joshu cannot view confidential security services or unconnected enterprise schedules.
PagerDuty's own AI features work inside the PagerDuty incident tools. Joshu is a dedicated teammate with memory across PagerDuty, Slack, Sentry, Jira, and email. It connects incident root causes to recent code deployments and compiles clear post-mortem briefs across multiple platforms.
Joshu is $95 a month after a 14-day free trial. That includes your sandboxed cloud computer, a dedicated US phone number, an @joshu.me email address, persistent memory across your tools, and all tool connectors, including PagerDuty. There are no token fees. Paid data and media APIs from the tool catalog are extra, paid per call from a prepaid usage wallet.