Henrik Solberg

Check out the documentation here: https://www.home-assistant.io/integrations/cover.group/ In short you just need to add the shutters you want to control as "one" to a group. You will then get a new...

Hi! We have a similar use-case. When more than one team use the same Pyrra and Prometheus-operator it's difficult to tell the alert-rules apart and Pyrra can get a little...

Thanks for the fast reply! Maybe I should create a separate issue for the frontend part since it's a separate thing? If you prefer to have "user-stories" tickets or specific...

Hi! A followup question, not sure if it should be asked here or in the closed ticket. The namespace label is used in Pyrra UI etc. but it doesn't seem...

I was just worried about potential issues with SSL validation, but it works just fine. Would be nice to have the option for a dedicated port either way for flexibility.

This looks very interesting for a similar use-case we have with a dedicated prometheus server. Would https://github.com/pyrra-dev/pyrra/pull/361 result in a dedicated binary that we could use in Ansible playbooks? Just...

> > If #361 results in a dedicated binary then we could create a playbook with ansible to generate the files based of the `slo.yaml` and send the files to...

That's understandable! As you said in other issues, you already have a long backlog, so I'm not expecting this to be a top priority 😄. Hopefully it's something that could...

Hi! Any updates here? This would be a fantastic addition to Pyrra. Especially on use cases for migration from OpenShift (on-prem) to AWS. Having Pyrra SLOs established on-prem to monitor...

@RiRa12621 We've successfully deployed this to our OpenShift cluster, but I can't confirm if the prometheus-operator logic works (the part where rules should be automatically picked up py prometheus-operator). We...