Describe the bug
When plugin crash this information is not forwarded to the standard log level.
For operators there is no indication that a fatal issue happened.
It requires "DEBUG" log level being enabled to see relevant logs, which is terrible for production systems
To Reproduce
Steps to reproduce the behavior:
Let the plugin crash, no error logged just a warning
[WARN] error closing client during Kill: err="rpc error: code = Canceled desc = grpc: the client connection is closing"
enable "debug" log level, now ERROR is logged like
[DEBUG] panic: runtime error: invalid memory address or nil pointer dereference
Expected behavior
Panics and such are not "debug" but "error" log level
Describe the bug When plugin crash this information is not forwarded to the standard log level. For operators there is no indication that a fatal issue happened.
It requires "DEBUG" log level being enabled to see relevant logs, which is terrible for production systems
To Reproduce Steps to reproduce the behavior:
[WARN] error closing client during Kill: err="rpc error: code = Canceled desc = grpc: the client connection is closing"
[DEBUG] panic: runtime error: invalid memory address or nil pointer dereference
Expected behavior Panics and such are not "debug" but "error" log level
Environment: