Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upScraping metrics that are behind a Basic Auth login #697
Comments
This comment has been minimized.
This comment has been minimized.
|
It's because the URL scheme has to move to the beginning. With the next version, basic auth can be configured in what now is the |
This comment has been minimized.
This comment has been minimized.
|
Oh, duh. Let me try that, thanks. On 5/14/15, Fabian Reinartz notifications@github.com wrote:
|
This comment has been minimized.
This comment has been minimized.
|
I assume the issue is resolved with that. |
fabxc
closed this
May 14, 2015
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
kmandeville commentedMay 14, 2015
I'm looking to monitor a Spring Boot app I have in production. Since it's in production, I didn't want people stumbling across the /metrics endpoints and others that come from actuator so I put them behind a username and password. I tried putting the username and password in the url in the config file which works in browsers:
username:password@http://blah.com/metrics
But that fails in Prometheus saying that "username" is not a valid protocol. So obviously it's not supported. Is there some way to configure the username and password for the metrics that I want prometheus to scrape?