Skip to content
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

CEL input runtime error source location reporting #37304

Closed
efd6 opened this issue Dec 6, 2023 · 1 comment · Fixed by #37718
Closed

CEL input runtime error source location reporting #37304

efd6 opened this issue Dec 6, 2023 · 1 comment · Fixed by #37718
Assignees
@efd6
Labels
enhancement Filebeat Filebeat

Comments

@efd6
Copy link
Contributor

efd6 commented Dec 6, 2023 •
edited
Loading

Debugging complex CEL inputs can sometimes be tricky when issues are found in production. This would be helped if the source location of runtime errors were reported in CEL logs.

I have made changes in the CEL runtime to support this, so we can add source location decoration to logs
@efd6 efd6 self-assigned this Dec 6, 2023
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Dec 6, 2023
@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Dec 6, 2023
@efd6 efd6 added the Filebeat Filebeat label Dec 6, 2023
This was referenced Jan 18, 2024
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@efd6 efd6

Labels
enhancement Filebeat Filebeat
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

x-pack/filebeat/input/cel: update mito version to v1.8.0 efd6/beats
2 participants
@elasticmachine @efd6