Daniel Clark

@belarminof or @ldurak are you still seeing these error messages with the latest image `gke.gcr.io/prometheus-engine/prometheus:v2.35.0-gmp.2-gke.0`?

@ImryLevySadan - thanks for reporting. Is this intermittent? Or is it constantly happening? And are you getting the exact same error as originally reported above?

Ok. I'm going to close the issue for now. Please reach out again if the issue re-occurs and we can take a closer look.

Note - this soon may be possible with https://github.com/prometheus/common/pull/416..

Hi @robmonct, Yes. We're tracking that work here and will hopefully have some updates soon.

Apologies @aniekgul - we're still working on rolling this out internally. Thanks for following up here though!

@mhoran IIUC this is more related to nginx ingress configuration more than the actual GMP query API, correct? If so, I'm tempted to close this issue as we don't have...

Yea makes sense. Thanks for the response! I'm going to close this. Feel free to re-open or file a new issue if there's any other issues and we can take...

Interesting. So IIUC the main reason we can't support the probe monitoring use case in a single `PodMonitoring` is that the `job_name`s are not unique if the `port`s are not...

Hi @QuerQue, 1. Yes. Managed collection can be left as you've currently configured it for node-exporter scraping. 2. Yes that workaround should work for deploying the GMP collector as a...