Paul Traylor
Paul Traylor
One more thing I would check, is that the promgen worker has permission to write the files. For example, if you created `promgen.rule.yml` as root, but then are running promgen...
There is no requirement for either to run as root. Typically it is better to run them as a non-root user. So for example you might create a new `prometheus`...
Do you have a shard and prometheus servers registered via the `/admin/` page ?
The URL for your cluster needs to be a real URL that Promgen can query. I think I also need to update the RuleTest to make the error more obvious
Can you also check `/admin/sites/site/` Ensure the promgen domain is the same as being served Going to work on two patches to help make this more obvious.
It's a good point. The existing flow is partly a result of the underlying Django model leaking through a bit, but it would not be too difficult to add.
Do you have ALLOWED_HOSTS set ? https://docs.djangoproject.com/en/3.1/ref/settings#allowed-hosts It's possible I do not have this documented well 🙇 You can set it to `*` to disable this check
It's not possible now, but I have thought about supporting custom labels and params for scrape targets. Promgen would likely still pass its default labels (job/service/project) though you could handle...
Currently there is no support for something like that 🙇
Prometheus is only reloaded, if you change exporters/rules. Changing the subscribed notifiers in Promgen does not trigger a reload.