Skip to content

Commit e756171

Browse files
authored
Merge pull request #204483 from yegu-ms/main
Adding conceptual article on high availability
2 parents f14cfab + 28730df commit e756171

File tree

3 files changed

+36
-1
lines changed

3 files changed

+36
-1
lines changed
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
title: High availability in Azure Managed Grafana Preview
3+
description: Learn about high availability options provided by Azure Managed Grafana Preview
4+
author: maud-lv
5+
ms.author: malev
6+
ms.service: managed-grafana
7+
ms.topic: conceptual
8+
ms.date: 6/18/2022
9+
---
10+
11+
# High availability in Azure Managed Grafana Preview
12+
13+
An Azure Managed Grafana Preview instance in the Standard tier is hosted on a dedicated set of virtual machines (VMs). By default, two VMs are deployed to provide redundancy. Each VM runs a Grafana server. A network load balancer distributes browser requests amongst the Grafana servers. On the backend, the Grafana servers are connected to a shared database that stores the configuration and other persistent data for an entire Managed Grafana instance.
14+
15+
:::image type="content" source="media/high-availability/high-availability.png" alt-text="Diagram of the Managed Grafana Standard tier instance setup.":::
16+
17+
The load balancer always keeps track of which Grafana servers are available. In a dual-server setup, if it detects that one server is down, the load balancer starts sending all requests to the remaining server. That server should be able to pick up the browser sessions previously served by the other one based on information saved in the shared database. In the meantime, the Managed Grafana service will work to repair the unhealthy server or bring up a new one.
18+
19+
## Zone redundancy
20+
21+
Normally the network load balancer, VMs and database that underpin a Managed Grafana instance are located within one Azure datacenter. The Managed Grafana Standard tier supports *zone redundancy*, which provides protection against zonal outages. When the zone redundancy option is selected, the VMs are spread across [availability zones](../availability-zones/az-overview.md#availability-zones) and other resources with availability zone enabled.
22+
23+
> [!NOTE]
24+
> Zone redundancy can only be enabled when creating the Managed Grafana instance, and can't be modified subsequently. There's also an additional charge for using the zone redundancy option. Go to [Azure Managed Grafana pricing](https://azure.microsoft.com/pricing/details/managed-grafana/) for details.
25+
26+
In a zone-wide outage, no user action is required. An impacted Managed Grafana instance will rebalance itself to take advantage of the healthy zone automatically. The Managed Grafana service will attempt to heal the affected instances during zone recovery.
27+
28+
## Next steps
29+
30+
> [!div class="nextstepaction"]
31+
> [Create an Azure Managed Grafana Preview instance](./quickstart-managed-grafana-portal.md)
81 KB
Loading

articles/managed-grafana/toc.yml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,11 @@ items:
1111
- name: Create an instance from the portal
1212
href: quickstart-managed-grafana-portal.md
1313
- name: Create an instance from the CLI
14-
href: quickstart-managed-grafana-cli.md
14+
href: quickstart-managed-grafana-cli.md
15+
- name: Concepts
16+
items:
17+
- name: High availability
18+
href: high-availability.md
1519
- name: How-to guides
1620
items:
1721
- name: Configure data source plugins

0 commit comments

Comments
 (0)