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

Document that you do not support environment variables #966

Closed
kaihendry opened this issue Sep 1, 2017 · 1 comment
Closed

Document that you do not support environment variables #966

kaihendry opened this issue Sep 1, 2017 · 1 comment

Comments

@kaihendry
Copy link

This is missing information from https://prometheus.io/docs/alerting/configuration/

Support for environment variables was bizarrely removed in #308 and it makes deploying alertmanager a total PITA as a result.

@brian-brazil
Copy link
Contributor

That page already documents what we do support, I don't think it's sane to list everything we don't support. For example we don't take configuration from other files, etcd or secure enclaves either.

hh pushed a commit to ii/alertmanager that referenced this issue Oct 11, 2018
* infiniband: Add not connected i40iw0/ports/1 fixtures
* infiniband: Handle issue when iWARP* RDMA modules are not available

This is related to prometheus#966, and handle this error,

Jun 07 13:33:24 hostname node_exporter[81888]: time="2018-06-07T13:33:24+02:00" level=error msg="ERROR: infiniband
collector failed after 0.000929s: strconv.ParseUint: parsing \"N/A (no PMA)\": invalid syntax" source="collector.go:132"

Signed-off-by: Mario Trangoni <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants