Skip to content

Commit 743787d

Browse files
authored
Remove API key usage limitation
1 parent e583853 commit 743787d

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/managed-grafana/known-limitations.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,9 @@ title: Azure Managed Grafana limitations
33
description: List of known limitations in Azure Managed Grafana
44
ms.service: managed-grafana
55
ms.topic: troubleshooting
6-
ms.date: 08/31/2022
6+
ms.date: 10/18/2022
77
ms.author: malev
8+
ms.custom:engagement-fy23
89
author: maud-lv
910
---
1011

@@ -24,8 +25,6 @@ Managed Grafana has the following known limitations:
2425

2526
* Querying Azure Data Explorer may take a long time or return 50x errors. To resolve these issues, use a table format instead of a time series, shorten the time duration, or avoid having many panels querying the same data cluster that can trigger throttling.
2627

27-
* API key usage isn't included in the audit log.
28-
2928
* Users can be assigned the following Grafana Organization level roles: Admin, Editor, or Viewer. The Grafana Server Admin role isn't available to customers.
3029

3130
* Some Data plane APIs require Grafana Server Admin permissions and can't be called by users. This includes the [Admin API](https://grafana.com/docs/grafana/latest/developers/http_api/admin/), the [User API](https://grafana.com/docs/grafana/latest/developers/http_api/user/#user-api) and the [Admin Organizations API](https://grafana.com/docs/grafana/latest/developers/http_api/org/#admin-organizations-api).

0 commit comments

Comments
 (0)