-
Notifications
You must be signed in to change notification settings - Fork 156
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
[logs_processors] Add support for lookup processors #287
[logs_processors] Add support for lookup processors #287
Conversation
44bf87a
to
c0c23af
Compare
Hi @bkabrda ! Could you have your 👀 on this PR? |
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.
Hey, this looks great, I just left one minor comment inline to address.
@@ -93,6 +94,14 @@ type GrokRule struct { | |||
MatchRules *string `json:"match_rules"` | |||
} | |||
|
|||
// LookupProcessor represents the lookup processor from config API. | |||
type LookupProcessor struct { | |||
Source *string `json:"source"` |
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.
The fields that are not required should be marked as omitempty
(IIUC that's default_lookup
)
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.
You're right! I have made the change 👌
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.
Perfect, LGTM now. Merging, thanks!
Add support for lookup processors, see https://docs.datadoghq.com/logs/processing/processors/?tab=ui#lookup-processor