We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Within the utils.go the blackbox_exporter tries to resolve the ip address of the target. https://github.com/prometheus/blackbox_exporter/blob/master/prober/utils.go#L34
can there be a config param to skip this resolve and use the dns name that should be checked?
example: to check: https://my_dns_entry:1234/service what blackbox_exporter does: https://1.2.3.4:1234/service
log: ts=2024-04-17T13:01:37.6789646Z level=debug msg="Resolved target address" component_path=/ component_id=prometheus.exporter.blackbox.network module=http_2xx target=https://my_dns_entry:1234/service target=my_dns_entry ip=1.2.3.4
ts=2024-04-17T13:01:37.6789646Z level=debug msg="Resolved target address" component_path=/ component_id=prometheus.exporter.blackbox.network module=http_2xx target=https://my_dns_entry:1234/service target=my_dns_entry ip=1.2.3.4
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Host operating system: RHEL8
blackbox_exporter version: 0.24.1
Within the utils.go the blackbox_exporter tries to resolve the ip address of the target.
https://github.com/prometheus/blackbox_exporter/blob/master/prober/utils.go#L34
can there be a config param to skip this resolve and use the dns name that should be checked?
example:
to check: https://my_dns_entry:1234/service
what blackbox_exporter does: https://1.2.3.4:1234/service
log:
ts=2024-04-17T13:01:37.6789646Z level=debug msg="Resolved target address" component_path=/ component_id=prometheus.exporter.blackbox.network module=http_2xx target=https://my_dns_entry:1234/service target=my_dns_entry ip=1.2.3.4
The text was updated successfully, but these errors were encountered: