Skip to content

[9.1](backport #45361) x-pack/filebeat/input/httpjson: allow empty cursor template values to be ignored by health status updates#45398

Merged
efd6 merged 1 commit into9.1from
mergify/bp/9.1/pr-45361
Jul 15, 2025
Merged

[9.1](backport #45361) x-pack/filebeat/input/httpjson: allow empty cursor template values to be ignored by health status updates#45398
efd6 merged 1 commit into9.1from
mergify/bp/9.1/pr-45361

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Jul 15, 2025

Proposed commit message

x-pack/filebeat/input/httpjson: allow empty cursor template values to be ignored by health status updates

Health status changes are evaluated in CI for integrations and in some
cases (aws.guardduty is the provocation here), there is a failed/empty
evaluation. So allow ignore_empty_value configurations for cursor
entries to also be ignored for health status updates, instead of being
noted as a health degradation.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

This is an automatic backport of pull request #45361 done by [Mergify](https://mergify.com).

@efd6 @mergify
x-pack/filebeat/input/httpjson: allow empty cursor template values to…
d88e768 
… be ignored by health status updates (#45361)

Health status changes are evaluated in CI for integrations and in some
cases (aws.guardduty is the provocation here), there is a failed/empty
evaluation. So allow ignore_empty_value configurations for cursor
entries to also be ignored for health status updates, instead of being
noted as a health degradation.

(cherry picked from commit 0257f0c)
@mergify mergify bot added the backport label Jul 15, 2025
@mergify mergify bot requested a review from a team as a code owner July 15, 2025 20:48
@mergify mergify bot assigned efd6 Jul 15, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jul 15, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jul 15, 2025

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@github-actions github-actions bot added enhancement Filebeat Filebeat Team:Security-Service Integrations Security Service Integrations Team labels Jul 15, 2025
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Jul 15, 2025

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jul 15, 2025
@efd6 efd6 enabled auto-merge (squash) July 15, 2025 20:53
@efd6 efd6 merged commit 3e79fed into 9.1 Jul 15, 2025
35 of 38 checks passed
@efd6 efd6 deleted the mergify/bp/9.1/pr-45361 branch July 15, 2025 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@efd6 efd6 efd6 approved these changes

Assignees

@efd6 efd6

Labels

backport enhancement Filebeat Filebeat Team:Security-Service Integrations Security Service Integrations Team

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@elasticmachine @efd6