[Feature Request] Distinc trigger for ERROR and CRITICAL failures

[arsenicks]

This is a feature request to adjust the Kometa integration to enable user to better manage failure notification. With the existing settings you can enable the 'Failure' trigger and the result is you appear to recieve notification for ERROR and (maybe) CRITICAL error level.

According to Kometa doc: https://metamanager.wiki/en/latest/kometa/logs/#understanding-log-file-event-types

ERROR: Error message that in MOST cases requires action on your part to resolve
CRITICAL: Critical message requiring you to fix it for Kometa to run properly

There's a lot of reasons why Kometa might throw ERROR, not all have to be acted on immediately. I want to recieve CRITICAL failure everytime they happen but I can manage ERROR in a monthly check for example. Currently the only way to not be notified on every run where there's error is to use a regex to ignore all ERROR or a list of errors.

And there's the notification message that add to the confusion by stating a "critical error has occured" which is not really true if it gets ERROR too.

Error
A critical error has occurred. Kometa has encountered an error with this collection. Check your local meta.log for more details.
Kometa
TMDb Error: No valid TMDb IDs in [YYYYY]

Wouldit be possible to separate ERROR and CRITICAL and fix the default message so things will be crystal clear and easier for everyone to select which level they want ?

Thanks!

[austinwbest]

This will be a lot easier if you hop on discord so we can discuss it. I need to see actual notifications with times, etc so i can pull logs. We can go back and forth via GH if you like but it will take significantly longer

[arsenicks]

Allright, I'll try to join tomorrow, what's the best time+timezone to catch you over there ?

[austinwbest]

EST and i am in/out basically all day every day. there is a feature request channel, just pop this in there and we can do some discussing on it from there