Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can I configure the web.external-url #288

Open
noesberger opened this issue Feb 9, 2024 · 2 comments · May be fixed by #320
Open

How can I configure the web.external-url #288

noesberger opened this issue Feb 9, 2024 · 2 comments · May be fixed by #320

Comments

@noesberger
Copy link

Hi

We need to specify the web.external-url for the pushgateway the same way we can for the prometheus itself.

In the template the only option I found to add additional configuration is in the web_config file:
--web.config.file=/etc/pushgateway/web_config.yml
with the variable:
pushgateway_http_server_config

But I can't find any documentations about what options to configure. And using
web.external-url=
is always failing. Any hints?

@gardar
Copy link
Member

gardar commented Feb 9, 2024

Hi, AFAIK the web.external-url option is a flag that should be passed to the binary and not a config file option for the web config.

I don't think it's possible to set the web.external-url for the pushgateway as the service template in the role does not have any options of specifying the external url and also does not have any option of passing in extra flags for the binary.

With that being said, PR's welcome.

@weakcamel weakcamel linked a pull request Mar 22, 2024 that will close this issue
@weakcamel
Copy link
Contributor

We also need the web.external-url parameter as we're running Pushgateway behind a reverse proxy (Caddy).

We've been using the CloudAlchemy role (https://github.com/cloudalchemy/ansible-pushgateway/tree/0.2.4) which I thought was the base for this community role, but when tryng to switch, I found the pushgateway_web_external_url parameter missing.

Here's a PR with this flag added (back?) and an additional "extra flags" parameter: #320

@gardar Does this look sensible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants