Paul Traylor

Prometheus targets can be in either json or yaml (though Promgen exports only json for targets) Prometheus rules are always yaml

Thanks for the report. I'll take a look 🙇

Right now, Rules must belong to either the Site (Global), Service, or Project, so it's not so surprising (to me) that trying to overwrite an alert for a single host...

Thank you for the report. I believe this is not a security issue as much as it's a documentation issue. For most of your api examples, that is expected behavior,...

Since Promgen is a tool for managing Prometheus, it follows many of the same assumptions as the Prometheus model https://prometheus.io/docs/operating/security/ It does not make much sense to implement IP checks...

`Cannot connect to amqp://guest:**@127.0.0.1:5672//:` suggests that the broker settings are incorrect. You need to add something similar to this to your environment for the web and worker nodes ```yaml environment:...

Promgen itself, defaults to Django's authentication framework though it supports oauth via [python-social-auth](https://python-social-auth.readthedocs.io/en/latest/backends/index.html) Right now there is no plan to support LDAP or SAM though perhaps there are similar frameworks...

In your case, can you try quoting it so that the shell does not escape things? `-e ALLOWED_HOSTS="*"`

Looking at your `promgen.yml` configuration, I see you use `/etc/prometheus/promgen.rule.yml` for your rule path. You should be able to check to see that it exists on your target Prometheus server....

And to confirm, you also have a `rule_files` section? https://github.com/line/promgen/blob/f83e51fe57b70bb7c162b10ab126bf5c3434705d/docker/prometheus.yml#L8-L11