We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe. As a user of the grok processor, I would like to tag the Events that timeout
Describe the solution you'd like Example for tagging on match failure (
data-prepper/data-prepper-plugins/grok-processor/src/main/java/org/opensearch/dataprepper/plugins/processor/grok/GrokProcessor.java
Line 263 in 3d8d01b
Can have a tag on timeout that will be tagged here (
Line 135 in 3d8d01b
Describe alternatives you've considered (Optional) A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Added in (#4032)
Sorry, something went wrong.
No branches or pull requests
Is your feature request related to a problem? Please describe.
As a user of the grok processor, I would like to tag the Events that timeout
Describe the solution you'd like
Example for tagging on match failure (
data-prepper/data-prepper-plugins/grok-processor/src/main/java/org/opensearch/dataprepper/plugins/processor/grok/GrokProcessor.java
Line 263 in 3d8d01b
Can have a tag on timeout that will be tagged here (
data-prepper/data-prepper-plugins/grok-processor/src/main/java/org/opensearch/dataprepper/plugins/processor/grok/GrokProcessor.java
Line 135 in 3d8d01b
Describe alternatives you've considered (Optional)
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: