{
  "site": "AIOps411",
  "edition_date": "2026-11-21",
  "stories": [
    {
      "id": "paige-on-call",
      "title": "PagerDuty can start Paige alongside the on-call responder",
      "summary": "An escalation policy can now start an investigation as soon as a matching incident opens. A manager chooses the incident scope and where Paige posts its findings.",
      "topic": "Triage",
      "date": "2026-11-19",
      "source": "PagerDuty",
      "url": "https://docs.pagerduty.com/ai-automation/advance/trigger-paige-via-escalation-policy"
    },
    {
      "id": "incident-list",
      "title": "PagerDuty starts rolling out bulk actions in the incidents list",
      "summary": "Responders can set priority or add responders across selected incidents. They can also start a workflow from an individual incident in the list.",
      "topic": "Response",
      "date": "2026-11-13",
      "source": "PagerDuty",
      "url": "https://docs.pagerduty.com/incident-management/incidents/navigate-incidents-page"
    },
    {
      "id": "closure-reason",
      "title": "PagerDuty adds a filter for why incidents were closed",
      "summary": "A responder can record a duplicate, a false alarm or a lasting fix at resolution. Teams can use that field to find noise in their incident queue.",
      "topic": "Incident review",
      "date": "2026-11-09",
      "source": "PagerDuty",
      "url": "https://docs.pagerduty.com/get-started/release-notes"
    },
    {
      "id": "collector-elastic",
      "title": "Collector Contrib drops obsolete Elasticsearch exporter settings",
      "summary": "Collector Contrib 0.165.0 rejects configurations that still use the retired options. Check exporters before an upgrade to keep logs, traces and metrics flowing.",
      "topic": "Telemetry",
      "date": "2026-11-07",
      "source": "OpenTelemetry",
      "url": "https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.165.0"
    },
    {
      "id": "collector-double-batch",
      "title": "OpenTelemetry Collector warns when a pipeline batches data twice",
      "summary": "Version 0.165.0 adds a startup warning when a batch processor feeds an exporter with its own batching. Its check stays within a single pipeline.",
      "topic": "Telemetry",
      "date": "2026-11-06",
      "source": "OpenTelemetry",
      "url": "https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.165.0"
    },
    {
      "id": "bits-times",
      "title": "Datadog reports shorter waits for Bits alert investigations",
      "summary": "Datadog says its investigations averaged about two minutes in October, down from eleven minutes at launch. The figures describe investigation time, a different measure from time to resolve an incident.",
      "topic": "Investigation",
      "date": "2026-11-02",
      "source": "Datadog",
      "url": "https://www.datadoghq.com/blog/bits-investigations-cost-speed-accuracy/"
    },
    {
      "id": "scout-launch",
      "title": "Datadog introduces Scout for investigating production incidents",
      "summary": "Scout 1.0 powers Bits Investigation. The model is designed to work through evidence from production systems when an on-call team needs a likely cause.",
      "topic": "Investigation",
      "date": "2026-10-15",
      "source": "Datadog",
      "url": "https://www.datadoghq.com/blog/ai/introducing-scout-sre-specialized-model-bits-ai/"
    },
    {
      "id": "bits-guardrails",
      "title": "Datadog previews guardrails for infrastructure remediation",
      "summary": "Teams can scope actions by resource and environment, then choose when an engineer must approve a proposed change.",
      "topic": "Remediation",
      "date": "2026-06-09",
      "source": "Datadog",
      "url": "https://www.datadoghq.com/blog/bits-infrastructure-operations/"
    }
  ],
  "records": [
    {
      "id": "paige-escalation",
      "name": "Paige on escalation policies",
      "platform": "PagerDuty",
      "category": "Triage",
      "status": "Generally available",
      "summary": "An on-call policy can start a parallel investigation while the human responder handles the page.",
      "events": [
        {
          "date": "2026-11-03",
          "label": "PagerDuty announced Paige as its SRE agent.",
          "source": "PagerDuty",
          "url": "https://www.pagerduty.com/newsroom/pagerduty-2026-fall-launch/"
        },
        {
          "date": "2026-11-19",
          "label": "PagerDuty released the escalation-policy trigger for Advance and PD Reliability Platform customers.",
          "source": "PagerDuty",
          "url": "https://docs.pagerduty.com/get-started/release-notes"
        }
      ],
      "facts": [
        {
          "label": "Trigger",
          "value": "An incident matches a policy with Paige enabled and falls within the selected scope.",
          "source": "PagerDuty",
          "url": "https://docs.pagerduty.com/ai-automation/advance/trigger-paige-via-escalation-policy"
        },
        {
          "label": "Action",
          "value": "Paige reads incident context, comparable past resolutions and connected logs or runbooks. It posts findings in PagerDuty or Slack.",
          "source": "PagerDuty",
          "url": "https://docs.pagerduty.com/ai-automation/advance/trigger-paige-via-escalation-policy"
        },
        {
          "label": "Human control",
          "value": "Managers and admins select the scope and destination. The responder receives the incident and can act while Paige investigates.",
          "source": "PagerDuty",
          "url": "https://docs.pagerduty.com/ai-automation/advance/trigger-paige-via-escalation-policy"
        }
      ]
    },
    {
      "id": "resolution-reason",
      "name": "Resolution reasons at incident close",
      "platform": "PagerDuty",
      "category": "Incident review",
      "status": "Rolling out",
      "summary": "Operations teams can filter resolved incidents by the reason a responder selected.",
      "events": [
        {
          "date": "2026-11-09",
          "label": "PagerDuty began rolling out the optional field to eligible plans.",
          "source": "PagerDuty",
          "url": "https://docs.pagerduty.com/get-started/release-notes"
        }
      ],
      "facts": [
        {
          "label": "Trigger",
          "value": "A responder opens the resolution form on a supported incident.",
          "source": "PagerDuty",
          "url": "https://docs.pagerduty.com/get-started/release-notes"
        },
        {
          "label": "Action",
          "value": "The closure reason becomes a filter in the Operations Console and PD Reliability Console. It gives Paige structured incident outcomes.",
          "source": "PagerDuty",
          "url": "https://docs.pagerduty.com/get-started/release-notes"
        },
        {
          "label": "Human control",
          "value": "The responder chooses whether to record a reason. The field starts enabled, and admins can edit or disable it under Incident Types.",
          "source": "PagerDuty",
          "url": "https://docs.pagerduty.com/get-started/release-notes"
        }
      ]
    },
    {
      "id": "bits-investigation",
      "name": "Bits monitor investigations",
      "platform": "Datadog",
      "category": "Investigation",
      "status": "Available",
      "summary": "Responders can launch an investigation from a monitor alert or configure a monitor to start one automatically.",
      "events": [
        {
          "date": "2026-10-15",
          "label": "Datadog introduced Scout 1.0, its specialized model for Bits Investigation.",
          "source": "Datadog",
          "url": "https://www.datadoghq.com/blog/ai/introducing-scout-sre-specialized-model-bits-ai/"
        },
        {
          "date": "2026-11-02",
          "label": "Datadog published its October averages for investigation duration and cost.",
          "source": "Datadog",
          "url": "https://www.datadoghq.com/blog/bits-investigations-cost-speed-accuracy/"
        }
      ],
      "facts": [
        {
          "label": "Trigger",
          "value": "A supported monitor enters its alert state with automatic investigation enabled, or a responder starts an investigation from an alert.",
          "source": "Datadog",
          "url": "https://docs.datadoghq.com/bits_ai/bits_investigation/investigate_issues/"
        },
        {
          "label": "Action",
          "value": "Bits tests possible causes against telemetry, runbooks and previous investigations. The findings can include inconclusive hypotheses.",
          "source": "Datadog",
          "url": "https://www.datadoghq.com/blog/bits-ai-sre/"
        },
        {
          "label": "Human control",
          "value": "Engineers choose which monitors launch investigations and can give feedback on a finding.",
          "source": "Datadog",
          "url": "https://docs.datadoghq.com/bits_ai/bits_investigation/investigate_issues/"
        }
      ]
    },
    {
      "id": "bits-infrastructure-actions",
      "name": "Bits infrastructure actions",
      "platform": "Datadog",
      "category": "Remediation",
      "status": "Preview",
      "summary": "An investigation can propose an infrastructure change and route it to the person or team authorized to approve it.",
      "events": [
        {
          "date": "2026-06-09",
          "label": "Datadog described its infrastructure remediation preview and demonstrated approval rules scoped by service and environment.",
          "source": "Datadog",
          "url": "https://www.datadoghq.com/blog/bits-infrastructure-operations/"
        }
      ],
      "facts": [
        {
          "label": "Trigger",
          "value": "Bits identifies a possible infrastructure fix during an investigation, such as rolling back a Kubernetes deployment.",
          "source": "Datadog",
          "url": "https://docs.datadoghq.com/bits_ai/bits_remediation/infrastructure_actions/"
        },
        {
          "label": "Action",
          "value": "The operator can approve a supported action in the investigation or through Slack. A matching guardrail must cover the resource and operation.",
          "source": "Datadog",
          "url": "https://docs.datadoghq.com/bits_ai/bits_remediation/infrastructure_actions/"
        },
        {
          "label": "Human control",
          "value": "Admins name approvers under an Ask rule. A Deny rule allows a recommendation while blocking execution.",
          "source": "Datadog",
          "url": "https://docs.datadoghq.com/bits_ai/bits_remediation/guardrails/"
        }
      ]
    },
    {
      "id": "collector-elasticsearch",
      "name": "Elasticsearch exporter configuration",
      "platform": "OpenTelemetry",
      "category": "Telemetry",
      "status": "Released",
      "summary": "Collector Contrib 0.165.0 removes several exporter options. An old configuration can interrupt telemetry delivery during rollout.",
      "events": [
        {
          "date": "2026-11-07",
          "label": "The Contrib release listed removed mapping, retry and dynamic indexing settings.",
          "source": "OpenTelemetry",
          "url": "https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.165.0"
        }
      ],
      "facts": [
        {
          "label": "Trigger",
          "value": "Collector Contrib loads an Elasticsearch exporter configuration that still contains a removed option.",
          "source": "OpenTelemetry",
          "url": "https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.165.0"
        },
        {
          "label": "Action",
          "value": "The configuration fails to load. The release notes list replacement settings for mapping mode and the retry count.",
          "source": "OpenTelemetry",
          "url": "https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.165.0"
        },
        {
          "label": "Human control",
          "value": "The pipeline owner can inspect the configuration before rollout and replace the retired keys, including retry::max_requests.",
          "source": "OpenTelemetry",
          "url": "https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.165.0"
        }
      ]
    },
    {
      "id": "collector-batching",
      "name": "Collector pipeline batching warning",
      "platform": "OpenTelemetry",
      "category": "Telemetry",
      "status": "Released",
      "summary": "The Collector can identify two layers of batching in the same telemetry pipeline during startup.",
      "events": [
        {
          "date": "2026-11-06",
          "label": "Collector core 0.165.0 added the startup diagnostic.",
          "source": "OpenTelemetry",
          "url": "https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.165.0"
        }
      ],
      "facts": [
        {
          "label": "Trigger",
          "value": "A pipeline includes both the batch processor and an exporter with visible exporterhelper batching.",
          "source": "OpenTelemetry",
          "url": "https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.165.0"
        },
        {
          "label": "Action",
          "value": "The Collector writes a startup warning. The check stops at connectors and can miss batching hidden by an exporter wrapper.",
          "source": "OpenTelemetry",
          "url": "https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.165.0"
        },
        {
          "label": "Human control",
          "value": "The operator reviews the affected pipeline and decides whether to change its batching configuration.",
          "source": "OpenTelemetry",
          "url": "https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.165.0"
        }
      ]
    }
  ]
}
