This repository was archived by the owner on Mar 8, 2023. It is now read-only.
HTTPS support with insecure verify option#86
Merged
grobie merged 3 commits intoprometheus:masterfrom Dec 16, 2017
Merged
Conversation
wdauchy
reviewed
Dec 13, 2017
haproxy_exporter.go
Outdated
Contributor
There was a problem hiding this comment.
could you squash this commit in the first one?
Updated the documentation
Member
|
Thanks! |
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In one of my projects haproxy_exporter is located on a different machine and should be able to communicate via HTTPS with certificate verification disabled.
Here is the pull request that solves the problem.
This pull request addresses Issue #74.