Okay I'll file a bug report in github.

On Saturday, November 7, 2020 at 3:49:32 AM UTC-6 Brian Brazil wrote:

> On Sat, 7 Nov 2020 at 08:21, Brian Candler <[email protected]> wrote:
>
>> On Friday, 6 November 2020 21:16:18 UTC, Brett Jacobson wrote:
>>>
>>> I am trying to set the proxy_url param on a scrape config job that uses 
>>> azure_sd_configs for azure service discovery.  It appears that the azure 
>>> service discovery module does not respect this setting from the 
>>> scrape_config block as documented here: 
>>> https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config
>>> .
>>>
>>>
>> https://groups.google.com/d/msg/prometheus-users/HdK6pr4ugwo/9f8KUFENCAAJ
>>
>> As I understand it, the proxy_url in the scrape job is only used when 
>> scraping the target, not when talking to the service discovery.
>>
>> Looking at the documentation 
>> <https://prometheus.io/docs/prometheus/latest/configuration/configuration/>, 
>> some of the service discovery mechanisms do support their own "proxy_url" 
>> setting, but azure_sd 
>> <https://prometheus.io/docs/prometheus/latest/configuration/configuration/#azure_sd_config>
>>  
>> isn't one of them.  If the underlying azure client library doesn't provide 
>> a proxy_url, that's probably why prometheus can't provide it either.  So 
>> you'd first need to make a PR on the underlying library, and get that 
>> merged, before doing the same for prometheus itself.
>>
>
> The preferred way to do it would be to be able to pass in a Transport, as 
> then our library for all the standard http options can be used rather than 
> having to re-implement them individually.
>
> -- 
> Brian Brazil
> www.robustperception.io
>

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/49330473-aee8-46a0-a15d-d7f89308e485n%40googlegroups.com.

Reply via email to