Alexander L.
Alexander L.
This would be nice to have. Would also be great to have the alerts solve themself automatically once they are not happening anymore.
For Opsgenie i just set the alias to the description, works out most of the time, as long as the description does not contain a time string that is always...
@stefanprodan True, guess the only way that would work would be to send messages for every run that was ok, which would be a little noisy.
@PatrickZeier-SAG how did you manage to enrich it with the cluster name? Did you just add more information to `spec. eventMetadata`? @stefanprodan i guess i would need to set the...
@PatrickZeier-SAG thanks that works perfectly! Now i just need to find a way to differentiate between errors, infos and recovery messages 😁
@PatrickZeier-SAG ah yeah that is one way of handling this. Thanks for the tip! Yeah me neither, i don't see a way on how a recovery message is different from...
Ok, i thought of doing it the way like @PatrickZeier-SAG suggested it. So to have two alerts for info and error. But as the info also contains the error part...
So with the changes from #796 i managed to set the `eventSeverity` to `info` and filtering on Opsgenie so only errors are made into an alert. However, i seem to...
Hey! With the latest version i also get the `network error` when using llama2 or llama3. If i just chat with the GPT directly it gives me a response. Just...
@gargmukku07 which value did you set for llama2?