Marcus Efraimsson

> Looking through Grafana change logs, I wonder if this change is related: > > #87884 @johannes-petzold-snow thanks. Are you sure you're using v11.1.0? In that case I don't think...

> Asking @grafana/plugins-platform-backend, has there ben any change to returning 414 errors? @bohandley not that I'm aware of and seems like 414 status is returned from the downstream Prometheus server

> 1. `CheckHealth` signature doesn't have headers. It's been supported since Grafana v9.2 https://grafana.com/docs/grafana/v9.2/developers/plugins/add-authentication-for-data-source-plugins/#forward-oauth-identity-for-the-logged-in-user Starting from Grafana v9.4 there's some helpers available to operate on forwarded HTTP headers https://grafana.com/docs/grafana/next/developers/plugins/add-authentication-for-data-source-plugins/#forward-oauth-identity-for-the-logged-in-user

> Main reasons why I submitted this issue: > > * ID Token is part of user identity (alongside with login, email, role), actually claims of ID Token describe the...

In addition, upgrade notes for v9.4.x: https://grafana.com/docs/grafana/next/developers/plugins/migration-guide/#from-version-93x-to-94x

> * Practical reason. There are three different types of request struct: query request, resource call and health check. When one component of business logic calls another component and wants...

> maybe a generic thought, what's the problem of having all the related logic in the same package? If there is no clear distinction between packages, I don't see the...

Closing for now since no direct interest, but could be picked up in the future if needed

FYI I've forked this repository, converted to go modules and tagged v0.1.0 https://github.com/marefr/go-conntrack. I'll consider this feature request there

It sounds/looks like you overload Grafana using the live feature. Profiles seems like you're using API keys for sending data to Grafana Live, please try migrate to service accounts since...