Change log level for elasticsearch errors input #2818
Conversation
|
@edsiper @mtparet I agree with this patch, the log statement is only enabled if the user turns on trace_error. If a user explicitly opts into more information reported on the plugin, I think they should get this info without enabling system-wide debug. TBH it would be ideal if we had per plugin log levels instead, but for now I think this patch is a good idea. |
Signed-off-by: Matthieu Paret <[email protected]>
|
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. |
|
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. |
Error level to get logs that failed to be ingested by elasticsearch is currently debug level.
I think there are many cases we want to understand what caused the failure without the flood of all others debug logs.
What do you think ?
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.