What is the Joshu PagerDuty connection?

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.

Is my PagerDuty data secure?

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.

Will Joshu resolve or reassign PagerDuty incidents without asking?

Joshu monitors and drafts by default. Acknowledging active incidents, overriding escalation policies, or resolving alerts follows approval rules you set, so on-call incident response remains in human control.

What can Joshu access in PagerDuty?

Only the PagerDuty accounts, services, and escalation policies authorized during OAuth sign-in. Joshu cannot view confidential security services or unconnected enterprise schedules.

What is the difference between PagerDuty native AI and Joshu?

PagerDuty native AI focuses on grouping alerts inside the active incident feed. 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.

Do I need a paid plan?

Joshu is $95 a month with a simple flat rate. That includes your sandboxed cloud computer, a dedicated US phone number, an @joshu.me email address, eight-level cortex memory, and all tool connectors, including PagerDuty. There are no surprise usage tiers or seat markups.

Home ConnectConnect Joshu to PagerDuty

Connect Joshu to PagerDuty

Connect PagerDuty so Joshu can check on-call schedules, review incident histories, and summarize infrastructure alerts for your team.

PagerDuty

“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.

“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.

“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 trigger immediate notifications for critical service breaches.

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 silence alerts or reconfigure escalation policies without explicit instruction.

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.
: Joshu monitors and drafts by default. Acknowledging active incidents, overriding escalation policies, or resolving alerts follows approval rules you set, so on-call incident response remains in human control.
: Only the PagerDuty accounts, services, and escalation policies authorized during OAuth sign-in. Joshu cannot view confidential security services or unconnected enterprise schedules.
: PagerDuty native AI focuses on grouping alerts inside the active incident feed. 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 with a simple flat rate. That includes your sandboxed cloud computer, a dedicated US phone number, an @joshu.me email address, eight-level cortex memory, and all tool connectors, including PagerDuty. There are no surprise usage tiers or seat markups.