Thomas Eizinger

Meeting summary from today with @bmanifold and @jamilbk: - Want to stick to OTEL to remain vendor-neutral - Don't want to use a 3rd party service so we have control...

I don't think the idea of using metabase to query these metrics will be workable. One of the most basic queries in PromQL is to calculate the rate of a...

I think we should just store these in Google Cloud metrics for now like we do for the relay and the portal. Google Cloud isn't the best frontend for writing...

@bmanifold I thought about your idea of enabling metrics on a per account basis. We can totally do that! Enabling the collection is global state anyway so we can do...

> Have you tried Metabase though? No I've never used it. I tried to sign-in to our metabase but when I click "Sign-In with Google", it does not allow me...

> With the timescale extension the rate query becomes: > > ``` > SELECT > time_bucket('1 minute', timestamp) AS bucket, > counter_rate( > counter_agg(timestamp, counter_value), > '5 minutes'::interval > )...

Sentry is working on a native OTEL endpoint but no mention of metrics unfortunately: https://github.com/getsentry/sentry/discussions/85902

Just to summarize, regardless of the query approach (metabase vs Google Cloud Metrics), we can agree that we need to run an OTEL collector in the cloud, right? Why can't...

With #9838, we now have a configuration option for sending metrics of a Gateway to an OTEL exporter. We can use that to trial these metrics with our GCP hosted...

It looks like Azure Metrics allow ingesting via OTEL and are designed to be publicly exposed to the Internet: https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/data-platform-metrics