-
Notifications
You must be signed in to change notification settings - Fork 115
Add community_id, fingerprint, and network_direction processors #3011
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
Conversation
Match the ConvertType enum to the values and order defined in Elasticsearch's ConverProcessor. https://github.com/elastic/elasticsearch/blob/a0cd389b43f4a155ae849e7730a8bcb6a9deb35f/modules/ingest-common/src/main/java/org/elasticsearch/ingest/common/ConvertProcessor.java#L31 Fixes #2309
|
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
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.
Thank you for contributing to the spec 🙂
I left some comments.
|
I just noticed that we have a |
internal_networks and internal_networks_field are mutually exclusive so they must both be optional.
| /** | ||
| * Object field containing extracted domain components. If an empty string, | ||
| * the processor adds components to the document’s root. | ||
| * @server-default <empty string> |
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.
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.
| * constructed with template snippets. Must specify only one of | ||
| * internal_networks or internal_networks_field. | ||
| */ | ||
| internal_networks: string[] |
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.
This is the one field that is almost an IP address where would could use the Ip[] type. But that would be inaccurate because the values can be a IP or a CIDR. Should I create a type alias for CIDR somewhere such that the type can be (Ip | CIDR)[]?
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.
Please refresh my memory. Is xxx.xxx.xxx.xxx without a slash a valid CIDR notation that defaults to /32?
In any way, I think it's fine keeping just string[] in this case.
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.
Please refresh my memory. Is xxx.xxx.xxx.xxx without a slash a valid CIDR notation that defaults to /32?
Yes, that's how the processor is behaving for ipv4. I didn't check it, but for ipv6 I would expect similar behavior just using /128 to indicate that it's matching one address.
e853e2f to
4982c5f
Compare
|
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
|
With this change, all of the processors and parameters used across elastic/integrations ingest pipelines are accounted for in the spec. |
|
Hi @andrewkroh, thanks for updating the PR. Looks good now 🙂 Let's just remove the |
|
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
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! thank you
…rocessors (#3011) Add ingest processor definitions for `community_id`, `fingerprint`, `network_direction`, and `registered_domain` processors. All parameters and descriptions were scraped from the 8.16 docs. Add `ip` to the list of types supported by the `convert` processor. Add `ecs_compatibility` to grok processor. Add `output_format` to date processor. Related issues - Fixes #2309 - Fixes #2553 - Fixes #2593 - Fixes #2617 (cherry picked from commit d1857ea)
…rocessors (#3011) (#3018) Add ingest processor definitions for `community_id`, `fingerprint`, `network_direction`, and `registered_domain` processors. All parameters and descriptions were scraped from the 8.16 docs. Add `ip` to the list of types supported by the `convert` processor. Add `ecs_compatibility` to grok processor. Add `output_format` to date processor. Related issues - Fixes #2309 - Fixes #2553 - Fixes #2593 - Fixes #2617 (cherry picked from commit d1857ea) Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
Add ingest processor definitions for
community_id,fingerprint,network_direction, andregistered_domainprocessors. All parameters and descriptions were scraped from the 8.16 docs.Add
ipto the list of types supported by theconvertprocessor.Add
ecs_compatibilityto grok processor.Add
output_formatto date processor.Related issues