You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have several many different dashboards in grafana that uses ADX plugin, many of them are associated with an "Application". We wish to know from the "Application" column in ADX, what is the application associated with it. We want to create a different datasource for each of these (querying the same adx cluster) - so we may track queries usage (performance, intervals, etc..).
We have hundreds of ADX queries in our grafana - many of them are under-performant.
This way we can track down the query owner and fix it.
Creating different tokens in azure per datasource for grafana is undesirable - we don't wish to create more tokens every time an "application" is added to grafana, but creating a new datasource is acceptable.
The solution
Adding the "Application" property to the adx datasource config, making it easier for us to identify where is the query coming from inside grafana .
The text was updated successfully, but these errors were encountered:
Use case
We have several many different dashboards in grafana that uses ADX plugin, many of them are associated with an "Application". We wish to know from the "Application" column in ADX, what is the application associated with it. We want to create a different datasource for each of these (querying the same adx cluster) - so we may track queries usage (performance, intervals, etc..).
We have hundreds of ADX queries in our grafana - many of them are under-performant.
This way we can track down the query owner and fix it.
Creating different tokens in azure per datasource for grafana is undesirable - we don't wish to create more tokens every time an "application" is added to grafana, but creating a new datasource is acceptable.
The solution
Adding the "Application" property to the adx datasource config, making it easier for us to identify where is the query coming from inside grafana .
The text was updated successfully, but these errors were encountered: