{"id":255,"date":"2025-06-23T07:12:35","date_gmt":"2025-06-23T07:12:35","guid":{"rendered":"http:\/\/sreschool.com\/blog\/?p=255"},"modified":"2026-05-05T07:30:04","modified_gmt":"2026-05-05T07:30:04","slug":"tutorial-on-call-rotation-in-devsecops","status":"publish","type":"post","link":"https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/","title":{"rendered":"Tutorial: On-call Rotation in DevSecOps"},"content":{"rendered":"\n

1. Introduction & Overview<\/strong><\/h2>\n\n\n\n

What is On-call Rotation?<\/h3>\n\n\n\n

On-call rotation is a structured schedule that distributes the responsibility of responding to alerts or incidents among team members, especially during off-hours. It ensures continuous monitoring and rapid incident response in systems that require 24\/7 availability.<\/p>\n\n\n\n

History or Background<\/h3>\n\n\n\n
    \n
  • Origin<\/strong>: Initially practiced in telecom and IT operations teams where uptime was mission-critical.<\/li>\n\n\n\n
  • Evolution<\/strong>: With the rise of DevOps and now DevSecOps, on-call rotation is no longer exclusive to operations\u2014it includes developers and security engineers too.<\/li>\n\n\n\n
  • Modernization<\/strong>: Integrated with automated alerting tools like PagerDuty, Opsgenie, and Slack + Prometheus.<\/li>\n<\/ul>\n\n\n\n

    Why is it Relevant in DevSecOps?<\/h3>\n\n\n\n
      \n
    • Always-on Security<\/strong>: Threats can occur anytime. An on-call schedule ensures a team is always ready to respond.<\/li>\n\n\n\n
    • Incident Response Integration<\/strong>: It\u2019s a key part of Incident Management\u2014an essential DevSecOps pillar.<\/li>\n\n\n\n
    • Compliance & SLAs<\/strong>: Many regulatory frameworks (e.g., HIPAA, SOC 2) require defined incident response procedures.<\/li>\n\n\n\n
    • Cultural Shift<\/strong>: Embeds ownership and accountability into security and operations.<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n

      2. Core Concepts & Terminology<\/strong><\/h2>\n\n\n\n

      Key Terms and Definitions<\/h3>\n\n\n\n
      Term<\/th>Definition<\/th><\/tr><\/thead>
      On-call Rotation<\/strong><\/td>A schedule that assigns engineers responsibility to monitor\/respond to alerts.<\/td><\/tr>
      Primary\/Secondary<\/strong><\/td>Primary is first to respond, secondary is backup if the primary is unavailable.<\/td><\/tr>
      Escalation Policy<\/strong><\/td>Rules that determine how alerts are passed if not acknowledged.<\/td><\/tr>
      Alert Fatigue<\/strong><\/td>Desensitization caused by frequent, repetitive, or false alarms.<\/td><\/tr>
      Runbook<\/strong><\/td>A set of documented steps to resolve known issues or respond to specific incidents.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      How It Fits into the DevSecOps Lifecycle<\/h3>\n\n\n\n

      On-call rotation supports the \u201cRespond\u201d<\/strong> and \u201cRecover\u201d<\/strong> phases:<\/p>\n\n\n\n

        \n
      • Plan<\/strong> \u2192 Build \u2192 Test \u2192 Release \u2192 Deploy \u2192 Monitor \u2192 Respond \u2192 Recover<\/em><\/li>\n\n\n\n
      • Integrated with:\n
          \n
        • SIEM tools for security alerts.<\/li>\n\n\n\n
        • Monitoring platforms for availability metrics.<\/li>\n\n\n\n
        • CI\/CD pipelines for post-deployment monitoring.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
          \n\n\n\n

          3. Architecture & How It Works<\/strong><\/h2>\n\n\n\n

          Components<\/h3>\n\n\n\n
            \n
          • Alert Sources<\/strong>: CloudWatch, Prometheus, Datadog, etc.<\/li>\n\n\n\n
          • Routing Engine<\/strong>: Defines rules for who gets notified (e.g., Opsgenie, PagerDuty).<\/li>\n\n\n\n
          • Notification Channels<\/strong>: Slack, Email, SMS, Phone.<\/li>\n\n\n\n
          • Escalation Policies<\/strong>: Chains of contact and wait times.<\/li>\n\n\n\n
          • Calendar\/Rotation Schedules<\/strong>: Define availability.<\/li>\n<\/ul>\n\n\n\n

            Internal Workflow<\/h3>\n\n\n\n
              \n
            1. Alert Triggered<\/strong> from Monitoring\/Logging tool.<\/li>\n\n\n\n
            2. Routing Engine Matches<\/strong> alert with the current on-call schedule.<\/li>\n\n\n\n
            3. Notification Sent<\/strong> to the primary on-call via preferred channel.<\/li>\n\n\n\n
            4. If not acknowledged<\/strong>, escalate to the next responder.<\/li>\n\n\n\n
            5. Incident Response Initiated<\/strong> using a runbook or documented process.<\/li>\n<\/ol>\n\n\n\n

              Architecture Diagram (Textual Description)<\/h3>\n\n\n\n
              [Monitoring Tools] \u2192 [Alert Routing (e.g., PagerDuty)] \u2192 [On-Call Schedule] \n   \u2192 [Primary Responder] \u2192 [Secondary Responder] \u2192 [Incident Management Tool]\n<\/code><\/pre>\n\n\n\n
              Integration Points with CI\/CD or Cloud Tools<\/h3>\n\n\n\n
                \n
              • Prometheus + Alertmanager<\/strong> for Kubernetes-based deployments.<\/li>\n\n\n\n
              • PagerDuty Webhooks<\/strong> triggered post-deployment (CI) failures.<\/li>\n\n\n\n
              • AWS CloudWatch Alarms<\/strong> integrated with Opsgenie.<\/li>\n\n\n\n
              • Slack + JIRA<\/strong> for automated ticketing on alert acknowledgement.<\/li>\n<\/ul>\n\n\n\n
                \n\n\n\n
                4. Installation & Getting Started<\/strong><\/h2>\n\n\n\n
                Basic Setup or Prerequisites<\/h3>\n\n\n\n
                  \n
                • Cloud Monitoring Service (e.g., AWS CloudWatch, Prometheus).<\/li>\n\n\n\n
                • Alert Management Tool (e.g., PagerDuty, Opsgenie).<\/li>\n\n\n\n
                • Slack or Email for notifications.<\/li>\n\n\n\n
                • CI\/CD tool (GitHub Actions, GitLab CI, Jenkins).<\/li>\n\n\n\n
                • Permissions to configure alert routing and integrations.<\/li>\n<\/ul>\n\n\n\n
                  Hands-on: Step-by-step Setup with PagerDuty + Prometheus<\/h3>\n\n\n\n
                  Step 1: Configure Prometheus Alertmanager<\/h4>\n\n\n\n
                  # alertmanager.yml\nroute:\n  receiver: 'pagerduty'\nreceivers:\n  - name: 'pagerduty'\n    pagerduty_configs:\n      - service_key: 'YOUR_SERVICE_KEY'\n<\/code><\/pre>\n\n\n\n
                  Step 2: Add PagerDuty Integration<\/h4>\n\n\n\n
                    \n
                  1. Log in to PagerDuty.<\/li>\n\n\n\n
                  2. Create a Service<\/strong> \u2192 Integration Type: Prometheus.<\/li>\n\n\n\n
                  3. Copy Service Integration Key<\/strong>.<\/li>\n\n\n\n
                  4. Paste it into alertmanager.yml<\/code>.<\/li>\n<\/ol>\n\n\n\n
                    Step 3: Set Up On-call Rotation<\/h4>\n\n\n\n
                      \n
                    • Navigate to Schedules<\/strong>.<\/li>\n\n\n\n
                    • Add team members.<\/li>\n\n\n\n
                    • Define rotation frequency (weekly, daily).<\/li>\n\n\n\n
                    • Configure escalation policy.<\/li>\n<\/ul>\n\n\n\n
                      Step 4: Test an Alert<\/h4>\n\n\n\n
                      curl -XPOST http:\/\/localhost:9093\/api\/v1\/alerts \\\n-d '[{\n  \"labels\": {\n    \"alertname\": \"HighCPUUsage\"\n  },\n  \"annotations\": {\n    \"summary\": \"Instance i-12345678 CPU usage > 90%\"\n  }\n}]'\n<\/code><\/pre>\n\n\n\n
                      \n\n\n\n
                      5. Real-World Use Cases<\/strong><\/h2>\n\n\n\n
                      1. Security Incident Response<\/strong><\/h3>\n\n\n\n
                        \n
                      • Scenario<\/strong>: IDS\/IPS system detects port scanning on cloud VMs.<\/li>\n\n\n\n
                      • On-call Rotation<\/strong>: Notifies security engineer on call to validate and mitigate.<\/li>\n<\/ul>\n\n\n\n
                        2. Post-deployment Failures<\/strong><\/h3>\n\n\n\n
                          \n
                        • Scenario<\/strong>: New deployment causes a memory leak.<\/li>\n\n\n\n
                        • On-call Rotation<\/strong>: DevSecOps engineer triages based on alert, reverts the deployment.<\/li>\n<\/ul>\n\n\n\n
                          3. DDoS Attack<\/strong><\/h3>\n\n\n\n
                            \n
                          • Scenario<\/strong>: Traffic anomaly from single region.<\/li>\n\n\n\n
                          • On-call Rotation<\/strong>: Network security specialist investigates, blocks IPs via firewall.<\/li>\n<\/ul>\n\n\n\n
                            4. Ransomware Alert in Finance Sector<\/strong><\/h3>\n\n\n\n
                              \n
                            • Industry-specific<\/strong>: Financial services must respond to malware alerts within 15 minutes (per regulation).<\/li>\n\n\n\n
                            • On-call Rotation<\/strong>: Guarantees SLA compliance through pre-defined rotations and escalation.<\/li>\n<\/ul>\n\n\n\n
                              \n\n\n\n
                              6. Benefits & Limitations<\/strong><\/h2>\n\n\n\n
                              Key Advantages<\/h3>\n\n\n\n
                                \n
                              • \u2705 Ensures 24\/7 availability.<\/li>\n\n\n\n
                              • \u2705 Reduces Mean Time To Resolution (MTTR).<\/li>\n\n\n\n
                              • \u2705 Encourages shared responsibility among teams.<\/li>\n\n\n\n
                              • \u2705 Supports compliance and auditability.<\/li>\n<\/ul>\n\n\n\n
                                Common Challenges<\/h3>\n\n\n\n
                                  \n
                                • \u26a0\ufe0f Alert Fatigue and burnout.<\/li>\n\n\n\n
                                • \u26a0\ufe0f Poor escalation policy leads to delayed responses.<\/li>\n\n\n\n
                                • \u26a0\ufe0f Requires cultural buy-in\u2014\u201cYou build it, you run it.\u201d<\/li>\n\n\n\n
                                • \u26a0\ufe0f Scheduling complexity in global teams.<\/li>\n<\/ul>\n\n\n\n
                                  \n\n\n\n
                                  7. Best Practices & Recommendations<\/strong><\/h2>\n\n\n\n
                                  Security Tips<\/h3>\n\n\n\n
                                    \n
                                  • Rotate and audit notification channels (e.g., phone numbers, emails).<\/li>\n\n\n\n
                                  • Use role-based access control (RBAC) for alert configuration.<\/li>\n\n\n\n
                                  • Store runbooks in version-controlled systems.<\/li>\n<\/ul>\n\n\n\n
                                    Performance & Maintenance<\/h3>\n\n\n\n
                                      \n
                                    • Regularly review and refine alert rules.<\/li>\n\n\n\n
                                    • Conduct post-incident reviews (PIRs).<\/li>\n\n\n\n
                                    • Test escalation policies quarterly.<\/li>\n<\/ul>\n\n\n\n
                                      Compliance Alignment<\/h3>\n\n\n\n
                                        \n
                                      • Log all alert acknowledgements and responses.<\/li>\n\n\n\n
                                      • Attach audit trails for GDPR, HIPAA, SOC 2 readiness.<\/li>\n<\/ul>\n\n\n\n
                                        Automation Ideas<\/h3>\n\n\n\n
                                          \n
                                        • Auto-create JIRA tickets on alert.<\/li>\n\n\n\n
                                        • Trigger rollback in CI\/CD if critical alert is triggered post-deploy.<\/li>\n\n\n\n
                                        • Auto-ping responder if acknowledgment doesn\u2019t occur in X mins.<\/li>\n<\/ul>\n\n\n\n
                                          \n\n\n\n
                                          8. Comparison with Alternatives<\/strong><\/h2>\n\n\n\n
                                          Feature \/ Tool<\/th>On-call Rotation<\/th>Slack Only Alerts<\/th>Email Forwarding<\/th>PagerDuty<\/th>Opsgenie<\/th><\/tr><\/thead>
                                          Escalation Policies<\/td>\u2705 Yes<\/td>\u274c No<\/td>\u274c No<\/td>\u2705 Yes<\/td>\u2705 Yes<\/td><\/tr>
                                          Schedule Management<\/td>\u2705 Yes<\/td>\u274c No<\/td>\u274c No<\/td>\u2705 Yes<\/td>\u2705 Yes<\/td><\/tr>
                                          CI\/CD Integration<\/td>\u2705 Yes<\/td>\u26a0\ufe0f Manual<\/td>\u274c No<\/td>\u2705 Yes<\/td>\u2705 Yes<\/td><\/tr>
                                          Audit Trails<\/td>\u2705 Yes<\/td>\u274c No<\/td>\u26a0\ufe0f Partial<\/td>\u2705 Yes<\/td>\u2705 Yes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                                          When to Choose On-call Rotation?<\/h3>\n\n\n\n
                                            \n
                                          • When system availability or security events require 24\/7 coverage.<\/li>\n\n\n\n
                                          • For teams with shared security and operational responsibilities.<\/li>\n\n\n\n
                                          • If SLA and compliance mandates are strict.<\/li>\n<\/ul>\n\n\n\n
                                            \n\n\n\n
                                            9. Conclusion<\/strong><\/h2>\n\n\n\n
                                            On-call rotation is a foundational practice in DevSecOps for maintaining uptime, ensuring rapid response to security incidents, and meeting compliance needs. As systems become more dynamic and distributed, well-managed on-call processes will continue to be critical.<\/p>\n\n\n\n
                                            Future Trends<\/h3>\n\n\n\n
                                              \n
                                            • AI-driven alert prioritization.<\/li>\n\n\n\n
                                            • Integration with chaos engineering for proactive issue detection.<\/li>\n\n\n\n
                                            • Gamification to reduce burnout.<\/li>\n<\/ul>\n\n\n\n
                                              \n\n\n\n
                                              <\/p>\n","protected":false},"excerpt":{"rendered":"
                                              1. Introduction & Overview What is On-call Rotation? On-call rotation is a structured schedule that distributes the responsibility of responding […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-255","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\nTutorial: On-call Rotation in DevSecOps - SRE School<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Tutorial: On-call Rotation in DevSecOps - SRE School\" \/>\n<meta property=\"og:description\" content=\"1. Introduction & Overview What is On-call Rotation? On-call rotation is a structured schedule that distributes the responsibility of responding […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/\" \/>\n<meta property=\"og:site_name\" content=\"SRE School\" \/>\n<meta property=\"article:published_time\" content=\"2025-06-23T07:12:35+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-05T07:30:04+00:00\" \/>\n<meta name=\"author\" content=\"priteshgeek\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"priteshgeek\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/tutorial-on-call-rotation-in-devsecops\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/tutorial-on-call-rotation-in-devsecops\\\/\"},\"author\":{\"name\":\"priteshgeek\",\"@id\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/#\\\/schema\\\/person\\\/6a53e3870889dd6a65b2e04b7bc3d7db\"},\"headline\":\"Tutorial: On-call Rotation in DevSecOps\",\"datePublished\":\"2025-06-23T07:12:35+00:00\",\"dateModified\":\"2026-05-05T07:30:04+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/tutorial-on-call-rotation-in-devsecops\\\/\"},\"wordCount\":854,\"commentCount\":0,\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/sreschool.com\\\/blog\\\/tutorial-on-call-rotation-in-devsecops\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/tutorial-on-call-rotation-in-devsecops\\\/\",\"url\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/tutorial-on-call-rotation-in-devsecops\\\/\",\"name\":\"Tutorial: On-call Rotation in DevSecOps - SRE School\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/#website\"},\"datePublished\":\"2025-06-23T07:12:35+00:00\",\"dateModified\":\"2026-05-05T07:30:04+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/#\\\/schema\\\/person\\\/6a53e3870889dd6a65b2e04b7bc3d7db\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/tutorial-on-call-rotation-in-devsecops\\\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/sreschool.com\\\/blog\\\/tutorial-on-call-rotation-in-devsecops\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/tutorial-on-call-rotation-in-devsecops\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Tutorial: On-call Rotation in DevSecOps\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/\",\"name\":\"SRESchool\",\"description\":\"Master SRE. Build Resilient Systems. Lead the Future of Reliability\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/#\\\/schema\\\/person\\\/6a53e3870889dd6a65b2e04b7bc3d7db\",\"name\":\"priteshgeek\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g\",\"caption\":\"priteshgeek\"},\"url\":\"https:\\\/\\\/sreschool.com\\\/blog\\\/author\\\/priteshgeek\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Tutorial: On-call Rotation in DevSecOps - SRE School","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/","og_locale":"en_US","og_type":"article","og_title":"Tutorial: On-call Rotation in DevSecOps - SRE School","og_description":"1. Introduction & Overview What is On-call Rotation? On-call rotation is a structured schedule that distributes the responsibility of responding […]","og_url":"https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/","og_site_name":"SRE School","article_published_time":"2025-06-23T07:12:35+00:00","article_modified_time":"2026-05-05T07:30:04+00:00","author":"priteshgeek","twitter_card":"summary_large_image","twitter_misc":{"Written by":"priteshgeek","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/#article","isPartOf":{"@id":"https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/"},"author":{"name":"priteshgeek","@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db"},"headline":"Tutorial: On-call Rotation in DevSecOps","datePublished":"2025-06-23T07:12:35+00:00","dateModified":"2026-05-05T07:30:04+00:00","mainEntityOfPage":{"@id":"https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/"},"wordCount":854,"commentCount":0,"inLanguage":"en","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/","url":"https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/","name":"Tutorial: On-call Rotation in DevSecOps - SRE School","isPartOf":{"@id":"https:\/\/sreschool.com\/blog\/#website"},"datePublished":"2025-06-23T07:12:35+00:00","dateModified":"2026-05-05T07:30:04+00:00","author":{"@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db"},"breadcrumb":{"@id":"https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/sreschool.com\/blog\/tutorial-on-call-rotation-in-devsecops\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sreschool.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Tutorial: On-call Rotation in DevSecOps"}]},{"@type":"WebSite","@id":"https:\/\/sreschool.com\/blog\/#website","url":"https:\/\/sreschool.com\/blog\/","name":"SRESchool","description":"Master SRE. Build Resilient Systems. Lead the Future of Reliability","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/sreschool.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en"},{"@type":"Person","@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db","name":"priteshgeek","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g","caption":"priteshgeek"},"url":"https:\/\/sreschool.com\/blog\/author\/priteshgeek\/"}]}},"_links":{"self":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/255","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/comments?post=255"}],"version-history":[{"count":1,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/255\/revisions"}],"predecessor-version":[{"id":256,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/255\/revisions\/256"}],"wp:attachment":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/media?parent=255"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/categories?post=255"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/tags?post=255"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}