-
Notifications
You must be signed in to change notification settings - Fork 468
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.
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
cel: new generic integration #5539
Conversation
🌐 Coverage report
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
This makes the Filebeat CEL input available as an integration package.
- name: event.dataset | ||
type: constant_keyword | ||
description: Event dataset | ||
value: cel.generic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With custom inputs I think having a static event.dataset
is problematic because users can customize the data stream.dataset
value. When they choose a value different than cel.generic
then data cannot be indexed due to the document not matching what is found in the mapping. So I think if you remove the value
so that it's like the data_stream.dataset
on line 4 it will be good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of our issues for event.dataset and data_stream.dataset (there are several other issues here as well like component templates) are all resolved if we move the package to be of type input
, as it has custom UI elements specifically for data_stream. Maybe we should look at that?
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Just in case, please do not merge it yet, I am trying to find some time this week at least to do a full review, since this is our first input type package, we should ensure it is in top shape, so we can use this as a template for future work 👍 |
No worries, merging this is blocked on a resolution to #5539 (comment) anyway. |
Option naming reflect that used in HTTPJSON (request instead of resource) for clarity and because we are tracing only requests, not all resource interactions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
This needs to be updated to make use of trace input ID substitution implemented as exists in HTTPJSON. |
Actually, the ID replacement functionality is not there yet. What would be your preference, merge this as is and change them both together, or change HTTPJSON to use the id-sub functionality and do the change for CEL here? |
IMO it can be merged without the ID replacement. We can push that update later and users shouldn't notice (except there will be a higher stack version requirement). |
Package cel - 0.1.0 containing this change is available at https://epr.elastic.co/search?package=cel |
What does this PR do?
This makes the Filebeat CEL input available as an integration package.
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots