๐Ÿ”ฅ
Developer Documentation
  • ๐Ÿ‘‹Welcome to Pagerly
  • How To Work With Pagerly
    • Get Started
    • ๐Ÿค‘Create Round Robin Rotations
      • ๐Ÿ“–How To Add Rotation in Pagerly
    • ๐Ÿ› ๏ธSetup Team
      • ๐Ÿ“–Retrieving Schedule Id for PagerDuty
      • ๐Ÿ“–Schedule for JSM Operations
      • ๐Ÿ“–Retrieving Schedule Id for OpsGenie
      • ๐ŸคFind Sheet Id from Google Sheets
      • ๐ŸคRetrieve Calendar Id from Google Calendar
    • ๐Ÿค‘Round-Robin Rotations for Tasks / Picking
      • ๐Ÿ“–How To Add Rotation for Picking Tasks in Pagerly
    • ๐Ÿค‘Round Robin Oncall without Schedule
      • ๐Ÿ“–How To Add Round Robin Rotation for Oncall without Schedule in Pagerly
    • ๐Ÿ˜ŽPlaying with Pagerly
      • ๐Ÿ‘€Mention Current Oncall on any Slack Conversation
      • ๐Ÿ•–Fetch your team's oncall schedule
      • ๐ŸŒ€Overriding Team's Schedule
      • ๐Ÿ—ฃ๏ธLet everyone know who is the Current Oncall of your Team
    • โฐReminders for Upcoming Rotation
    • Pagerduty Sync Slack and Workflows
    • ๐Ÿ”‘Setup Team Access
    • ๐Ÿ› ๏ธIntegrating with Your Paging Tool
      • ๐Ÿ“Retrieving PagerDuty API Key
      • ๐Ÿ“Connect JSM Operations
      • ๐Ÿ“Retrieving OpsGenie API Key
    • Escalations
    • ๐Ÿ—’๏ธIntegration with Jira
      • ๐ŸคAdd Your JIRA Account
      • ๐ŸžCreate a Ticket via Emoji and Follow on Slack Channel
      • ๐ŸงตPost Ticket created on Jira to Slack Thread
      • ๐Ÿš๏ธPost Ticket created on Jira to on Slack Channel
      • ๐Ÿ‘€Create Ticket via Slack Emoji and Follow on Slack Thread
      • ๐Ÿ“œCreate Jira Ticket/Incident using Form
      • ๐Ÿ”„Round Robin Assignment of Jira Issues/Tickets
    • ๐Ÿ“ŸSet Slack Status Automatically
    • ๐Ÿ“†Sync Schedule with Google Calendar
    • Creating Ticket via Emojis
    • ๐Ÿ”„Rotate & Assign Requests
    • ๐Ÿ”„Round Robin Assignment of Jira Issues/Tickets
    • ๐Ÿ”„Round Robin Assignment of Alerts/Incidents (Opsgenie/JSM Ops)
    • Instant Status Pages
    • ๐ŸคMention/Group Multiple Oncals
      • Configure MultiMention Team
    • ๐Ÿ› ๏ธLinear Integration
      • Connect Linear Account
      • Connect Pagerly Team and Linear Team
    • Create Swap on Oncall / Rotations
    • ๐Ÿ”„Custom Change Notification on Slack
    • ๐Ÿ“†Google Calendar with Slack
      • ๐ŸคRetrieve Calendar Id from Google Calendar
    • ๐Ÿ‘จGoogle Groups To Slack Usergroups
      • ๐ŸคFind Sheet Id from Google Sheets
    • Google Sheets with Slack
      • ๐ŸคFind Sheet Id from Google Sheets
    • ๐Ÿ“’Manage Tasks within Slack
    • Microsoft Team Setup
    • Discord App
    • ๐Ÿ‘ฉโ€โš•๏ธHelp and Support
    • ๐Ÿ Self Hosted
    • ๐Ÿ“ŠDaily Oncall Standup
    • ๐Ÿ’ฐCloud Cost App
      • ๐Ÿ› ๏ธSetup IAM Role for Temporary Access
      • ๐Ÿ› ๏ธConfiguring Team for Cloud Cost
  • ๐Ÿ‘จโ€๐Ÿš’Incidence Response
    • ๐ŸงฏPagerly Incidence Response
    • ๐Ÿ“–Overview
      • ๐ŸŽฅVideo Demo
    • ๐Ÿ˜Customization & Workflow
    • โš’๏ธIntegrations
    • ๐Ÿ Self Hosted
    • ๐Ÿ‘ฉโ€๐Ÿ’ผContact Us
Powered by GitBook
On this page

Was this helpful?

  1. Incidence Response

Customization & Workflow

We realise each team and engineers love to according to the workflows they like

With Pagerly services, you have the ability to create your own workflows and customize them according to your needs.At Pagerly, we understand the unique needs of your organization. Our platform offers extensive customization options to tailor the incident management process to your specific requirements. From incident workflows to report formatting, we put you in control.

Feel free to reach out to our support team for personalized assistance with customizing your incident management setup. We're here to help you get the most out of Pagerly and ensure seamless incident management for your business.

Following is the NOT AN EXHAUSTIVE LIST of customisation we support. These are the common themes we have encountered for customisation

  1. 1.Ticket routing and creation

    1. 1.Severity SLA

    2. 2.Ticketing Board

    3. 3.Assignee

    4. 4.Action Items :

      1. 1.Ticketing Board

      2. 2.Assignee

    5. 5.Taggings: Labels and Components

  2. 2.RCA Templates Root Cause Analysis (RCA) is a crucial process for identifying the underlying causes of incidents or issues. Our platform provides customizable RCA templates to streamline the RCA process and ensure comprehensive incident analysis. With our RCA templates, you can:

    • Document incident details, timelines, and affected services.

    • Identify contributing factors and potential causes of the incident.

    • Conduct a thorough investigation to pinpoint the root cause.

    • Propose and implement effective corrective and preventive actions.

    • Collaborate with teams to gain insights and build a knowledge base.

  3. 3.Teams and Services

    • Service Categorization: Group your technical services into logical categories based on their functionalities or ownership, making it simple to identify which teams are responsible for each service.

    • Incident Routing: Set up automatic incident routing based on the affected service. When an incident occurs, it will be directed to the appropriate team or team members responsible for that specific service.

    • Service Ownership: Assign clear ownership for each technical service, enabling efficient communication and accountability during incident resolution.

    • Dependencies Mapping: Map dependencies between services to better understand the impact of an incident on other interconnected services. This aids in prioritizing incident response efforts.

  4. Links for DebuggingTo streamline the debugging process and expedite incident resolution, our platform offers links with popular debugging tools.

  5. 5.RunbookEnsuring all incident response procedures and best practices are readily available during critical situations. With the Runbook integration, you can:

    • Access detailed step-by-step instructions and procedures for incident resolution.

  6. 6.ReportingOur platform empowers you with customizable incident reports and analytics to improve incident management. Generate insightful reports to:

    • Track incident trends and patterns over time.

    • Monitor the efficiency of RCA and incident resolution efforts.

    • Identify areas for improvement and implement data-driven changes.

PreviousVideo DemoNextIntegrations

Last updated 1 year ago

Was this helpful?

๐Ÿ‘จโ€๐Ÿš’
๐Ÿ˜