-
Notifications
You must be signed in to change notification settings - Fork 174
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
exporter: Use fqdn instead of hostname only #1290
exporter: Use fqdn instead of hostname only #1290
Conversation
This would break many existing setups where users have a |
Interesting, thank you for your quick feedback! As for the proxy, yes this does work and some of my colleagues use it that way. But I also expect drawbacks in forcing all traffic through the exporter and thought it as solution for some use cases only (e.g. remote/VPN, "difficult" networks outside administration control) but not the standard where name resolution into different subnets works. |
a6c7230
to
cd76271
Compare
cd76271
to
803f19f
Compare
As suggested by @Bastian-Krause, I just pushed a rework introducing a flag --fqdn to change the default when no --hostname is given. |
Please also update the man page under |
803f19f
to
44a051c
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1290 +/- ##
========================================
- Coverage 63.0% 63.0% -0.1%
========================================
Files 160 160
Lines 11901 11910 +9
========================================
+ Hits 7502 7504 +2
- Misses 4399 4406 +7 ☔ View full report in Codecov by Sentry. |
44a051c
to
d46aaa7
Compare
In distributed setups, the coordinator may point to exporters/places in different subnets. In order for clients to resolve resources behind the exporter, they need to know its FQDN instead of just the hostname. Using an option to change the default avoids conflicts for configs which rely on the hostname only. Signed-off-by: Andreas Naumann <[email protected]>
d46aaa7
to
6fb3fa2
Compare
Description
In distributed setups, the coordinator may point to places in different subnets. In order for clients to resolve resources behind the exporter, they need to know its FQDN instead of just the hostname.
Thus, set this to be the default when the exporter is invoked without the --hostname parameter.
Checklist