out_gelf: accept possible level values #2257
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed with myself in #2256, the restrictions on log level in GELF is a should, and also it is an optional field; so it doesn't seem to have a hard restriction on level value, as Graylog accepts the non-standard levels.
So I changed the attempt to be some kind of best-effort to match with standards, but if it's not, send it anyway and just throw a warning.
This PR also adds invocation of an error when level is not a string or a non-negative integer (As I haven't seen any negative log level and I think other data types mustn't be valid, yes?)
Testing
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.