Skip to content

[elastic_agent] Update status_change alerting rule templates for namespace routing - #20904

Open
Nikshaan wants to merge 2 commits into
elastic:mainfrom
Nikshaan:fix/286395-status-change-namespace-alerting-templates
Open

[elastic_agent] Update status_change alerting rule templates for namespace routing#20904
Nikshaan wants to merge 2 commits into
elastic:mainfrom
Nikshaan:fix/286395-status-change-namespace-alerting-templates

Conversation

@Nikshaan

@Nikshaan Nikshaan commented Aug 25, 2026

Copy link
Copy Markdown

Summary

Fixes elastic/kibana#286395 and elastic/kibana#287194

This change sends Fleet agent status change events to the policy namespace rather than always default. These templates use the FROM logs-elastic_agent.status_change-default pattern in their ES|QL queries, without this fix, alerting would not match events for any non-default namespace agent policies once the Kibana fix goes out.

Changes

Updated the ES|QL FROM clause in all 4 status-based alerting rule templates to logs-elastic_agent.status_change-* from logs-elastic_agent.status_change-default:

  • elastic-agent-offline-status.json
  • elastic-agent-unhealthy-status.json
  • elastic-agent-unenrolled-status.json
  • elastic-agent-uninstalled-status.json

No other changes were made to these files.

Note

Existing rules created from these templates (prior to this fix) are separate copies and will not get this change automatically - marking for feedback on whether we need a release note or migration.

Version

Version bumped for elastic_agent package from 2.9.4 to 2.9.5, changelog entry added.

Copilot AI lite review requested due to automatic review settings August 25, 2026 21:52
@Nikshaan
Nikshaan requested review from a team as code owners August 25, 2026 21:52

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Reviewers

Buildkite won't run for external contributors automatically; you need to add a comment:

  • /test : will kick off a build in Buildkite.

NOTE: https://github.com/elastic/integrations/blob/main/.buildkite/pull-requests.json contains all those details.

Copilot AI review requested due to automatic review settings August 25, 2026 21:55

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@juliaElastic

Copy link
Copy Markdown
Contributor

/test

@github-actions

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

✅ All changelog entries have the correct PR link.

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

💚 Build Succeeded

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Fleet] Agent status change events always land in the default namespace

3 participants