arik

Thanks for reporting it @kayahk and @Noamstrauss We're going to implement the parameters presets in the UI. For now, as a workaround, you can save the URL of a specific...

Thank you for reporting this @IdeoG Do you have any `customPlaybooks` configured? If so, can you please share your `customPlaybooks` section ? (Please make sure not to share any sensitive...

Typically, Robusta installation has the `values.yaml` file, which is the `defaults` file, and the `generated_values.yaml` file, which is the `overrides` file. Is it configured this way on your installation as...

Can you please share your `generated_values.yaml` file (without the sensitive values, if there are any)

Can you explain when you'd like to get a notification on `telegram`? For example, when a `deployment` is created, or when a `statefulset` is changed?

Thank you In general, when adding new playbooks, you should use the `customPlaybooks` value, and not the `builtinPlaybooks` Specifically, regarding your use cases: 1. Deployment update ``` - triggers: -...

@IdeoG , did the above configuration solve your use cases?

Thank you for reporting it @Ph3nol Can you describe a little the need to get the notifications on PushOver? Can Telegram sink be useful to you? https://docs.robusta.dev/master/catalog/sinks/telegram.html#telegram We also used...

Hi @vmusaely , I think you can achieve what you need by filtering the alert trigger only on firing alerts (and not resolved) Your playbook configuration in your `values.yaml` file...

Yes, we did. `on_prometheus_alert` is triggered, by default, only for `firing` alerts. Closing it