x-pack/filebeat/input/httpjson: allow empty cursor template values to be ignored by health status updates #45361
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
efd6
added
enhancement
Filebeat
botelastic
bot
added
needs_team
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
5 tasks
… 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.
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
andrewkroh
approved these changes
Jul 15, 2025
efd6
changed the title
mergify bot
pushed a commit
that referenced
this pull request
Jul 15, 2025
… 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 bot
pushed a commit
that referenced
this pull request
Jul 15, 2025
… 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)
This was referenced Jul 15, 2025
mergify bot
pushed a commit
that referenced
this pull request
Jul 15, 2025
… 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)
6 tasks
efd6
added a commit
that referenced
this pull request
Jul 15, 2025
… be ignored by health status updates (#45361) (#45396) 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) Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
efd6
added a commit
that referenced
this pull request
Jul 15, 2025
… be ignored by health status updates (#45361) (#45398) 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) Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
efd6
added a commit
that referenced
this pull request
Jul 15, 2025
…rsor template values to be ignored by health status updates (#45397) * x-pack/filebeat/input/httpjson: allow empty cursor template values to 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) * remove irrelevant changelog entries --------- Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs