-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Exit with failure when [SERVICE] fails to process #2637
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Cameron Moberg <[email protected]>
parser.config
To test, simply comment out one |
Debug log - duplicate parser name:
debug log invalid parser config
|
The below is valgrind with my change.
The below is a valgrind at HEAD using -R instead of `Parsers_File:
|
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
Fluent-bit, when with only the -c flag will only [error] log PARSER parsing errors. However, this has the unintended side-effect of just not continuing parsing parsers instead of the expected parsing failure log & skip.
For example, if there is parser A, B, C, and there is an error in parser B it will get logged, but it will NOT halt the execution of the program and only parser A will be parsed/applied.
Addresses #2480
Testing
Before we can approve your change; please submit the following in a comment:
Documentation
Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.