Lee Yanco

Yes, still working on this. AP is tricky, as you've encountered. We're working on making this on by default so all this struggle goes away.

AP still not supported - the latest news is we are almost done with 1.25 support, and then will make it work on 1.24. Stay tuned.

Could you share your project numbers with us so we can investigate? You can email them to me at (my github username) at (the company I work for) .com

Hey Will, We're working hard on official Autopilot support - once that's out we can see if this still happens or if it's only happening because of the unofficial way...

It's pretty unlikely we will support counter exemplars in the near term. In Monarch, exemplars are stored with the point itself, and only histograms have the necessary data structure (proto)...

Regarding why we don't support Counter exemplars - this might not be a satisfying answer, but we intentionally don't aim to maintain 100% compatibility with OSS Prometheus. Our goal is...

+1 - agreed on your assessment, upon further review it looks like once 2.45 is rolled out this issue will fix itself automatically. We're still qualifying it... should be soon...

Also - to add to my previous statement about pegging to new versions - we are Fedramp compliant w.r.t. patching CVEs and vulnerabilities. This all happens behind the scenes.

Note that Cloud Alerting PromQL does support generic webhook channels: https://cloud.google.com/monitoring/support/notification-options#webhooks

There are no scrape configurations installed by default in new clusters, even with managed Prometheus on by default. Therefore as long as you don't install any scrape configs you won't...