-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
enhancement(gcp_chronicle sink): Add default fallback logic if log_type template cannot be resolved fo… #22323
enhancement(gcp_chronicle sink): Add default fallback logic if log_type template cannot be resolved fo… #22323
Conversation
…r Google Chronicle sink
changelog.d/changelog.d/add_default_fallback_index_google_chronicle_sink.enhancement.md
Fixed
Show fixed
Hide fixed
40d8e47
to
25f0f17
Compare
Hey @ArunPiduguDD, do you need a review on this? It's marked as a draft but I am getting notifications because you tagged me as a reviewer. Happy to review when it's ready. |
@pront Just marked it as ready for review |
Datadog ReportBranch report: ✅ 0 Failed, 7 Passed, 0 Skipped, 25.49s Total Time |
Summary
Similar to changes made for the Elasticsearch and Object Storage sinks
Currently, the Google Chronicle sink has the option to specify an log_type to attach to events. This field supports template syntax, however if the template is not able to be resolved, the default behavior is to drop the event.
Adding an optional field that specifies a default fallback log_type that can be used if there is a template rendering error.
Testing
Tested using Vector pipeline with a Google Chronicle sink