{"id":58729,"date":"2026-02-13T01:25:08","date_gmt":"2026-02-13T01:25:08","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=58729"},"modified":"2026-02-13T01:25:34","modified_gmt":"2026-02-13T01:25:34","slug":"sre-incident-leadership-stability-incident-command-interrogation-and-influence-without-authority","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/sre-incident-leadership-stability-incident-command-interrogation-and-influence-without-authority\/","title":{"rendered":"SRE Incident Leadership &amp; Stability \u2014  Incident Command, Interrogation, and Influence Without Authority"},"content":{"rendered":"\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link wp-element-button\">Contact us &#8211; contact@DevOpsSchool.com<\/a><\/div>\n<\/div>\n\n\n\n<p><strong>SRE Incident Leadership &amp; Stability \u2014 Google-style Incident Command, Interrogation, and Influence Without Authority<\/strong><\/p>\n\n\n\n<p><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">What this workshop is based on (industry + Google SRE)<\/h2>\n\n\n\n<p>This agenda blends:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Google SRE incident management mindset<\/strong> (3Cs: coordinate, communicate, control; clear roles like IC\/Comms\/Ops; single live incident state document)<\/li>\n\n\n\n<li><strong>Google SRE troubleshooting + alerting philosophy<\/strong> (systematic troubleshooting; alerts should be actionable and symptom-oriented)<\/li>\n\n\n\n<li><strong>Google SRE stability levers<\/strong> (SLOs + error budgets as the \u201cauthority-less\u201d mechanism to shift priorities)<\/li>\n\n\n\n<li><strong>Industry incident response practice<\/strong> (Incident Commander training patterns; blameless postmortems; modern incident workflow tooling)<\/li>\n\n\n\n<li><strong>Modern learning-from-incidents \/ resilience engineering<\/strong> (learning-focused incident analysis; coordination costs; systemic fixes)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">3-Day Workshop Agenda (with labs + exercises)<\/h1>\n\n\n\n<h3 class=\"wp-block-heading\">Daily structure (recommended)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>60% practice<\/strong> (simulations, role-plays, artifacts)<\/li>\n\n\n\n<li><strong>40% concepts\/tools<\/strong> (frameworks, playbooks, decision patterns)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Day 1 \u2014 Incident Command + Structured Interrogation in Unknown Systems<\/h2>\n\n\n\n<p><strong>Goal:<\/strong> Enable PSREs to walk into an unfamiliar incident and still drive fast, clean outcomes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) The \u201cGoogle-style\u201d major incident operating system (IMAG\/ICS)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Why incident response fails (freelancing, unclear roles, weak comms, no single-threaded control)<\/li>\n\n\n\n<li><strong>3Cs<\/strong>: coordinate \/ communicate \/ control<\/li>\n\n\n\n<li>Core roles and how they work together: <strong>IC, Comms Lead, Ops Lead, Scribe<\/strong>\n<ul class=\"wp-block-list\">\n<li>Why roles ignore reporting lines and focus on execution clarity<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>The \u201csingle writer\u201d and \u201csingle source of truth\u201d: <strong>live incident state document<\/strong><\/li>\n\n\n\n<li>Severity model and operating cadence: declare, stabilize, update, resolve, review<\/li>\n<\/ul>\n\n\n\n<p><strong>Exercise:<\/strong> \u201cActivate in 5 minutes\u201d drill<br>Set roles, create war-room channel, start incident doc, set update cadence, define first 3 objectives.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">2) Structured incident interrogation (questioning system)<\/h3>\n\n\n\n<p>Teach a repeatable questioning framework PSREs can run <strong>without deep system knowledge<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Impact &amp; scope<\/strong> (who\/what is affected, blast radius, user journeys)<\/li>\n\n\n\n<li><strong>Time &amp; change<\/strong> (when started; what changed; last deploy\/config\/infra change)<\/li>\n\n\n\n<li><strong>Signals<\/strong> (best symptom metric; error\/latency patterns; what\u2019s normal baseline)<\/li>\n\n\n\n<li><strong>Dependencies<\/strong> (upstream\/downstream; what relies on what; isolate candidates)<\/li>\n\n\n\n<li><strong>Hypotheses + tests<\/strong> (top 3 likely causes; fastest tests to confirm\/deny)<\/li>\n\n\n\n<li><strong>Mitigation decision<\/strong> (stop bleeding vs diagnose; safe rollback vs forward fix)<\/li>\n<\/ul>\n\n\n\n<p><strong>Lab:<\/strong> Build a \u201cFirst 15 Minutes\u201d interrogation sheet + decision checkpoints<br>(Participants leave with a one-page checklist and question bank.)<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">3) Running the room under ambiguity (war-room mechanics)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Keeping tempo: time-boxing, checkpoints, and workstream split<\/li>\n\n\n\n<li>Preventing freelancing: only Ops executes changes; everyone else feeds evidence<\/li>\n\n\n\n<li>Handling SME conflict: how IC arbitrates with evidence + risk framing<\/li>\n\n\n\n<li>Communication discipline: what updates must include (impact, actions, ETA, risks)<\/li>\n<\/ul>\n\n\n\n<p><strong>Simulation #1 (tabletop):<\/strong> \u201cUnknown service outage\u201d<br>Limited context + conflicting SME opinions + noisy signals<br><strong>Outputs:<\/strong> live incident doc, timeline, hypothesis board, comms updates, decision log.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Day 2 \u2014 Navigating Architectures &amp; Dependencies + Observability-Driven Investigation<\/h2>\n\n\n\n<p><strong>Goal:<\/strong> Make PSREs effective at \u201cfinding the system\u201d fast and driving investigations cleanly.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Rapid architecture discovery (when docs are missing)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u201cWhiteboard the service\u201d method:\n<ul class=\"wp-block-list\">\n<li>request path, data stores, queues, caches, third parties, auth, network edges<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Dependency interrogation:\n<ul class=\"wp-block-list\">\n<li>what changed, what fans out, what is hard dependency, what degrades gracefully<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\u201cIsolation moves\u201d playbook:\n<ul class=\"wp-block-list\">\n<li>shed load, disable feature, bypass dependency, traffic shift, circuit breaker, rollback<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p><strong>Exercise:<\/strong> Build a 10-minute architecture map from SMEs using structured prompts.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">2) Observability tactics that work in war rooms<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Symptom-first investigation:\n<ul class=\"wp-block-list\">\n<li>identify best \u201cuser pain\u201d signal, then trace to components<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Practical workflow:\n<ul class=\"wp-block-list\">\n<li>RED\/USE signals, golden paths, service graphs, trace-to-logs<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Evidence preservation:\n<ul class=\"wp-block-list\">\n<li>what to snapshot (dashboards, logs, traces, configs, deployments) before changes<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Choosing where to look first:\n<ul class=\"wp-block-list\">\n<li>\u201ctop suspect list\u201d rules to avoid random debugging<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p><strong>Lab:<\/strong> Guided investigation flow on demo system<br>Participants practice: symptom \u2192 isolate \u2192 confirm\/deny hypotheses \u2192 mitigation choice.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">3) Comms excellence + handoffs<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>IC\/Comms templates (internal + external)<\/li>\n\n\n\n<li>Status update cadence and message quality<\/li>\n\n\n\n<li>Clean handoff protocol (explicit transfer of command; state doc update)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Simulation #2 (hands-on, tool-based)<\/h3>\n\n\n\n<p>Run a live incident game on a demo system:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Inject failure (latency, error spike, dependency degradation, partial outage)<\/li>\n\n\n\n<li>PSREs rotate roles (IC \/ Ops \/ Comms \/ Scribe)<\/li>\n\n\n\n<li>Scoring on: interrogation quality, control, speed, protocol adherence, comms clarity<\/li>\n<\/ul>\n\n\n\n<p><strong>End-of-day artifact pack:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incident channel checklist<\/li>\n\n\n\n<li>Incident state doc template<\/li>\n\n\n\n<li>Interrogation question bank<\/li>\n\n\n\n<li>Workstream board template<\/li>\n\n\n\n<li>Mitigation decision log template<\/li>\n\n\n\n<li>Handoff checklist<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Day 3 \u2014 Driving Stability Without Authority + Resilient Mindset (Operating in a Matrix Org)<\/h2>\n\n\n\n<p><strong>Goal:<\/strong> Turn PSREs into stability leaders who can influence priorities and create accountability.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) The \u201cauthority-less\u201d levers: SLOs + Error Budgets (Google SRE style)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Defining reliability outcomes: SLIs vs SLOs (what matters to users)<\/li>\n\n\n\n<li>Error budgets as the alignment mechanism:\n<ul class=\"wp-block-list\">\n<li>when budget burns, reliability work gets priority<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>What an error budget policy typically includes:\n<ul class=\"wp-block-list\">\n<li>release rules, mitigation requirements, reliability triggers, escalation path<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Using these levers diplomatically:\n<ul class=\"wp-block-list\">\n<li>\u201cpermission to pause\u201d with shared rules, not blame<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p><strong>Workshop:<\/strong> Draft an error budget policy skeleton suitable for your org.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">2) Influence without authority (practical playbook)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Stakeholder mapping:\n<ul class=\"wp-block-list\">\n<li>owners, decision makers, blockers, allies, exec sponsors, customer-facing teams<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Persuasion with evidence:\n<ul class=\"wp-block-list\">\n<li>incident themes, toil metrics, reliability risks, customer impact, near-misses<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Creating cross-team accountability:\n<ul class=\"wp-block-list\">\n<li>DRIs, RACI, due dates, measurable outcomes<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Operating cadence:\n<ul class=\"wp-block-list\">\n<li>weekly stability review, top risks register, actions tracking, escalation rituals<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p><strong>Role-play:<\/strong> \u201cCompeting priorities negotiation\u201d<br>Participants practice getting buy-in when the team says: \u201cfeature work first.\u201d<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">3) Blameless learning \u2192 stability roadmap<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Postmortem quality:\n<ul class=\"wp-block-list\">\n<li>timeline, contributing factors, detection gaps, decision analysis, action quality<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Turning postmortems into stability work:\n<ul class=\"wp-block-list\">\n<li>reduce recurrence, improve detection, reduce MTTR, reduce toil<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Tracking follow-ups:\n<ul class=\"wp-block-list\">\n<li>owners, deadlines, verification, and closure criteria<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p><strong>Lab:<\/strong> Write a \u201cblameless postmortem\u201d from the Day 2 simulation and derive the top 5 stability actions.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">4) Resilience mindset under pressure (personal + team)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cognitive traps in incidents:\n<ul class=\"wp-block-list\">\n<li>tunnel vision, confirmation bias, authority bias, panic-driven changes<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\u201cCalm operator\u201d habits:\n<ul class=\"wp-block-list\">\n<li>checkpoints, asking better questions, controlling pace, safe mitigation choices<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Sustaining effectiveness:\n<ul class=\"wp-block-list\">\n<li>fatigue management, handoffs, psychological safety, aftercare<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Capstone (must-do): 90-day Stability Influence Plan<\/h3>\n\n\n\n<p>Each team produces a <strong>90-day Stability Influence Plan<\/strong> for a real service:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>top reliability risks + supporting evidence<\/li>\n\n\n\n<li>proposed SLOs + measurement plan<\/li>\n\n\n\n<li>error budget policy proposal<\/li>\n\n\n\n<li>roadmap (quick wins + structural changes)<\/li>\n\n\n\n<li>stakeholders + comms plan + cadence<\/li>\n\n\n\n<li>accountability model (DRIs, due dates, review checkpoints)<\/li>\n<\/ul>\n\n\n\n<p><strong>Outputs:<\/strong> a plan you can directly take into leadership review.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Prerequisites (participants)<\/h1>\n\n\n\n<p><strong>Must-have<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Comfortable with Linux CLI basics and reading logs<\/li>\n\n\n\n<li>Basic understanding of microservices + HTTP behavior (latency, errors, dependencies)<\/li>\n<\/ul>\n\n\n\n<p><strong>Good-to-have<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Familiarity with Kubernetes concepts (pods\/services) or your runtime equivalent<\/li>\n\n\n\n<li>Basic knowledge of metrics\/logs\/traces (even beginner level is fine)<\/li>\n<\/ul>\n\n\n\n<p><strong>Pre-reading (short, high impact)<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incident roles and the 3Cs (coordinate\/communicate\/control)<\/li>\n\n\n\n<li>Managing incidents with a live incident state document<\/li>\n\n\n\n<li>Systematic troubleshooting methodology<\/li>\n\n\n\n<li>Error budgets and how they shift reliability vs feature priorities<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">Lab setup and tools (recommended)<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">Lab environment (choose one approach)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Option A (easiest): Docker-based microservices demo + built-in observability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Run a demo microservices app locally with metrics\/logs\/traces enabled<\/li>\n\n\n\n<li>Use simple failure injection:\n<ul class=\"wp-block-list\">\n<li>add latency, drop requests, stop a dependency container, overload a service<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p>Best when: participants have mixed environments and you want low friction.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Option B (most realistic): Kubernetes-based microservices demo + chaos injection<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Run a demo microservices app on a local Kubernetes cluster (kind\/minikube) or a shared training cluster<\/li>\n\n\n\n<li>Use fault injection:\n<ul class=\"wp-block-list\">\n<li>pod kill, network latency, packet loss, CPU\/memory pressure, dependency failures<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p>Best when: your real production environment is Kubernetes and you want realism.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Tools involved<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">War-room collaboration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Slack or Teams (incident channel + pinned checklist)<\/li>\n\n\n\n<li>Video call (Zoom\/Meet\/Teams)<\/li>\n\n\n\n<li>Shared incident state doc (Google Docs \/ Confluence \/ internal wiki)<\/li>\n\n\n\n<li>Optional: incident workflow tool (any modern \u201cincident timeline + roles + comms\u201d platform)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Observability (hands-on)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Metrics: Prometheus + Grafana (or vendor equivalent)<\/li>\n\n\n\n<li>Logs: Elastic\/Splunk\/Loki (or equivalent)<\/li>\n\n\n\n<li>Traces: Jaeger\/Tempo (or equivalent)<\/li>\n\n\n\n<li>Optional instrumentation pipeline: OpenTelemetry-style collection<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Reliability management artifacts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SLO dashboard (even if basic)<\/li>\n\n\n\n<li>Error budget burn reporting<\/li>\n\n\n\n<li>Postmortem template + action tracker<\/li>\n\n\n\n<li>Stability risk register (top risks, owners, target dates)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Failure injection (for gamedays)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Basic: container stop\/restart, load generation, latency injection<\/li>\n\n\n\n<li>Kubernetes: chaos tooling (pod kill, network faults, resource pressure)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">What participants will leave with (deliverables)<\/h1>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incident Command checklist (roles, cadence, comms)<\/li>\n\n\n\n<li>\u201cFirst 15 minutes\u201d interrogation sheet + question bank<\/li>\n\n\n\n<li>Incident state doc template + decision log + handoff checklist<\/li>\n\n\n\n<li>Investigation workflow guide (symptom \u2192 isolate \u2192 confirm \u2192 mitigate)<\/li>\n\n\n\n<li>Postmortem template + action quality rubric<\/li>\n\n\n\n<li>Draft error budget policy<\/li>\n\n\n\n<li>90-day Stability Influence Plan template + a completed plan for one service<\/li>\n\n\n\n<li>Simulation scorecard rubric (so you can repeat drills internally)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n","protected":false},"excerpt":{"rendered":"<p>SRE Incident Leadership &amp; Stability \u2014 Google-style Incident Command, Interrogation, and Influence Without Authority What this workshop is based on (industry + Google SRE) This agenda blends: 3-Day Workshop Agenda (with labs + exercises) Daily structure (recommended) Day 1 \u2014 Incident Command + Structured Interrogation in Unknown Systems Goal: Enable PSREs to walk into an&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_joinchat":[],"footnotes":""},"categories":[11138],"tags":[],"class_list":["post-58729","post","type-post","status-publish","format-standard","hentry","category-best-tools"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/58729","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=58729"}],"version-history":[{"count":2,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/58729\/revisions"}],"predecessor-version":[{"id":58731,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/58729\/revisions\/58731"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=58729"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=58729"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=58729"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}