Skip to content

[9.0](backport #45810) x-pack/filebeat/input/httpjson: allow template termination without logging error #45996

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Aug 19, 2025
Merged

[9.0](backport #45810) x-pack/filebeat/input/httpjson: allow template termination without logging error #45996

merged 2 commits into from
Aug 19, 2025
+30 −1

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Aug 13, 2025

Proposed commit message

x-pack/filebeat/input/httpjson: allow template termination without logging error

This adds a terminate helper that can be used to signal that a template
should terminate without an error. The termination can (should) be used
to report the reason for the termination which will be logged at DEBUG
level, but otherwise ignored.

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 #45810 done by [Mergify](https://mergify.com).

@efd6 @mergify
x-pack/filebeat/input/httpjson: allow template termination without lo…
d399d37 
…gging error (#45810)

This adds a terminate helper that can be used to signal that a template
should terminate without an error. The termination can (should) be used
to report the reason for the termination which will be logged at DEBUG
level, but otherwise ignored.

(cherry picked from commit f324f29)
@mergify mergify bot added the backport label Aug 13, 2025
@mergify mergify bot requested review from a team as code owners August 13, 2025 20:58
@mergify mergify bot assigned efd6 Aug 13, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Aug 13, 2025
@elasticmachine
Copy link
Collaborator

elasticmachine commented Aug 13, 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 Aug 13, 2025
@botelastic
Copy link

botelastic bot commented Aug 13, 2025

This pull request doesn't have a Team:<team> label.

@github-actions
Copy link
Contributor

github-actions bot commented Aug 13, 2025 •
edited
Loading

🔍 Preview links for changed docs

@mergify
Copy link
Contributor Author

mergify bot commented Aug 18, 2025

This pull request has not been merged yet. Could you please review and merge it @efd6? 🙏

efd6
efd6 reviewed Aug 19, 2025
View reviewed changes
@efd6 efd6 enabled auto-merge (squash) August 19, 2025 07:21
@efd6 efd6 merged commit b23125c into 9.0 Aug 19, 2025
26 of 29 checks passed
@efd6 efd6 deleted the mergify/bp/9.0/pr-45810 branch August 19, 2025 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@colleenmcginnis colleenmcginnis colleenmcginnis approved these changes

@efd6 efd6 efd6 approved these changes

Assignees

@efd6 efd6

Labels

backport bugfix 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.

4 participants

@elasticmachine @colleenmcginnis @efd6