Skip to content

Commit ea261a8

Browse files
committed
Updated based on feedback
1 parent d61ae5a commit ea261a8

File tree

2 files changed

+6
-5
lines changed

2 files changed

+6
-5
lines changed

articles/managed-grafana/high-availability.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ ms.author: malev
66
ms.service: managed-grafana
77
ms.topic: conceptual
88
ms.date: 7/27/2022
9+
ms.custom: references_regions
910
---
1011

1112
# Azure Managed Grafana service reliability

articles/managed-grafana/known-limitations.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,15 +16,15 @@ Azure Managed Grafana delivers the native Grafana functionality in the highest p
1616

1717
Managed Grafana has the following known limitations:
1818

19-
1. All users must have accounts in an Azure Active Directory. Microsoft (also known as MSA) and 3rd-party accounts aren't supported. As a workaround, use the default tenant of your Azure subscription with your Grafana instance and add other users as guests.
19+
* All users must have accounts in an Azure Active Directory. Microsoft (also known as MSA) and 3rd-party accounts aren't supported. As a workaround, use the default tenant of your Azure subscription with your Grafana instance and add other users as guests.
2020

21-
1. Installing, uninstalling and upgrading plugins from the Grafana Catalog aren't allowed.
21+
* Installing, uninstalling and upgrading plugins from the Grafana Catalog aren't allowed.
2222

23-
1. Data source query results are capped at 80 MB. To mitigate this constraint, reduce the size of the query, for example, by shortening the time duration.
23+
* Data source query results are capped at 80 MB. To mitigate this constraint, reduce the size of the query, for example, by shortening the time duration.
2424

25-
1. 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.
25+
* 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.
2626

27-
1. API key usage isn't included in the audit log.
27+
* API key usage isn't included in the audit log.
2828

2929
## Next steps
3030

0 commit comments

Comments
 (0)