Skip to content

[9.1](backport #45399) x-pack/filebeat/input/cel: attempt to harmonise single events with ECS #45508

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
Open
wants to merge 1 commit into
base: 9.1
Choose a base branch
from
Open

[9.1](backport #45399) x-pack/filebeat/input/cel: attempt to harmonise single events with ECS #45508

wants to merge 1 commit into from
+18 −2

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jul 22, 2025

Proposed commit message

x-pack/filebeat/input/cel: attempt to harmonise single events with ECS

If the object contains an error field, optimistically render the full
object as an ECS-compliant document, otherwise fall back to the
previously documented behaviour of rendering the document as an error.

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

@efd6 @mergify
x-pack/filebeat/input/cel: attempt to harmonise single events with ECS (
ecb1dfa 
#45399)

If the object contains an error field, optimistically render the full
object as an ECS-compliant document, otherwise fall back to the
previously documented behaviour of rendering the document as an error.

(cherry picked from commit afb28b2)
@mergify mergify bot added the backport label Jul 22, 2025
@mergify mergify bot requested review from a team as code owners July 22, 2025 20:34
@mergify mergify bot added the backport label Jul 22, 2025
@mergify mergify bot assigned efd6 Jul 22, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jul 22, 2025
@github-actions GitHub Actions
Copy link
Contributor

🤖 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 Team:Security-Service Integrations Security Service Integrations Team labels Jul 22, 2025
@elasticmachine
Copy link
Collaborator

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 22, 2025
@github-actions GitHub Actions
Copy link
Contributor

🔍 Preview links for changed docs

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

@efd6 efd6

Labels
backport enhancement 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