Funnily enough I was exploring that post yesterday - it came up based on 
some of the keywords I was searching for. Definitely useful to see someone 
breaking down the various possible data sources. I missed the part right at 
the bottom (the UPDATE) - it's helpful to see that. 
<host>:10255/metrics/cadvisor is the url my prometheus config is currently 
scraping. Still no luck there, but at least nice to be able to confirm that 
I'm not scraping the completely wrong place.
On Tuesday, September 1, 2020 at 2:17:55 AM UTC-7 [email protected] wrote:

> On Tuesday, 1 September 2020 06:51:29 UTC+1, Max Furman wrote:
>>
>> It's odd to me that the path I got from the examples is /metrics/advisor, 
>> but the path I queried using `kubectl get` was /proxy/metrics/advisor. 
>>
>>
> This is not well documented, but I think it's the difference between 
> scraping the kubelet directly versus scraping through the k8s API.
>
> I did attempt to reverse-engineer some of this here:
> https://discuss.kubernetes.io/t/list-of-prometheus-metrics-endpoints/9406
> but I wouldn't say I really got to the bottom of it.
>
>

-- 
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/818169f7-d115-4cae-9eaf-1612f9b4a3f4n%40googlegroups.com.

Reply via email to