You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
external_url
Data type: Optional[Variant[Stdlib::HTTPUrl, Stdlib::Unixpath, String[1]]]
The URL under which Alertmanager is externally reachable (for example, if Alertmanager is served via a reverse proxy). Used for generating relative and absolute links back to Alertmanager itself. If omitted, relevant URL components will be derived automatically.
I've found that it's necessary to use the alertmanager extra_options param instead to configure alertmanager's external URL:
I think this is a documentation issue, and that the docs for the prometheus::external_url parameter should be updated to say something like "The URL under which Prometheus is externally reachable..."
It might also be good to add a prometheus::alertmanager::external_url parameter for specifying the alertmanager external URL instead of having to use the extra_options.
The text was updated successfully, but these errors were encountered:
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Hieradata as follows:
What are you seeing
The external url gets configured for the prometheus service instead of the alertmanager service, contrary to what the docs say (https://forge.puppet.com/modules/puppet/prometheus/11.1.0/reference#external_url)
I've found that it's necessary to use the alertmanager
extra_options
param instead to configure alertmanager's external URL:What behaviour did you expect instead
I think this is a documentation issue, and that the docs for the prometheus::external_url parameter should be updated to say something like "The URL under which Prometheus is externally reachable..."
It might also be good to add a
prometheus::alertmanager::external_url
parameter for specifying the alertmanager external URL instead of having to use theextra_options
.The text was updated successfully, but these errors were encountered: