aolmosj

JFYI, the native cri parser stores de raw json app message in the 'message' field, while this repo custom parser stores a cri log format in the 'log' field. Even...

What do you mean? There is no need to change the INPUT section, since this setting in the current INPUT: `Parser cri` is using the fluent-bit native cri parser.

Yes, you are right. I left that unused custom parser there for future reference, since this PR is a workaround for a fluent-bit bad implementation of `Merge_log`. But It could...

What about an option to open the new session tab next to the active tab? I'm using tab groups and it's a pain because the new tab is open out...