Skip to content

Commit 731dad2

Browse files
committed
Adding remote-write docs to TOC
1 parent 8f0d9be commit 731dad2

File tree

5 files changed

+45
-6
lines changed

5 files changed

+45
-6
lines changed
14.8 KB
Loading
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
title: Get started with Azure Monitor Managed Service for Prometheus
3+
description: Get started with Azure Monitor managed service for Prometheus, which provides a Prometheus-compatible interface for storing and retrieving metric data.
4+
author: EdB-MSFT
5+
ms.service: azure-monitor
6+
ms-author: edbaynash
7+
ms.topic: conceptual
8+
ms.date: 02/15/2024
9+
---
10+
11+
# Get Started with Azure Monitor managed service for Prometheus
12+
13+
The only requirement to enable Azure Monitor managed service for Prometheus is to create an [Azure Monitor workspace](azure-monitor-workspace-overview.md), which is where Prometheus metrics are stored. Once this workspace is created, you can onboard services that collect Prometheus metrics.
14+
15+
- To collect Prometheus metrics from your Kubernetes cluster, see [Enable monitoring for Kubernetes clusters](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana).
16+
- To configure remote-write to collect data from your self-managed Prometheus server, see [Azure Monitor managed service for Prometheus remote write](./remote-write-prometheus.md).
17+
18+
## Data sources
19+
20+
Azure Monitor managed service for Prometheus can currently collect data from any of the following data sources:
21+
22+
- Azure Kubernetes service (AKS)
23+
- Azure Arc-enabled Kubernetes
24+
- Any server or Kubernetes cluster running self-managed Prometheus using [remote-write](./remote-write-prometheus.md).
25+
26+
## Next steps
27+
28+
- [Learn more about Azure Monitor Workspace](./azure-monitor-workspace-overview.md)
29+
- [Enable Azure Monitor managed service for Prometheus on your Kubernetes clusters](../containers/kubernetes-monitoring-enable.md).
30+
- [Configure Prometheus alerting and recording rules groups](prometheus-rule-groups.md).
31+
- [Customize scraping of Prometheus metrics](prometheus-metrics-scrape-configuration.md).

articles/azure-monitor/essentials/prometheus-metrics-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,14 +21,14 @@ Azure Monitor managed service for Prometheus allows you to collect and analyze m
2121
Azure Monitor managed service for Prometheus can currently collect data from any of the following data sources:
2222

2323
- Azure Kubernetes service (AKS)
24-
- Any Kubernetes cluster running self-managed Prometheus using [remote-write](https://aka.ms/azureprometheus-promio-prw).
25-
- Azure Arc-enabled Kubernetes
24+
- Azure Arc-enabled Kubernetes
25+
- Any server or Kubernetes cluster running self-managed Prometheus using [remote-write](./remote-write-prometheus.md).
2626

2727
## Enable
2828
The only requirement to enable Azure Monitor managed service for Prometheus is to create an [Azure Monitor workspace](azure-monitor-workspace-overview.md), which is where Prometheus metrics are stored. Once this workspace is created, you can onboard services that collect Prometheus metrics.
2929

3030
- To collect Prometheus metrics from your Kubernetes cluster, see [Enable monitoring for Kubernetes clusters](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana).
31-
- To configure remote-write to collect data from your self-managed Prometheus server, see [Azure Monitor managed service for Prometheus remote write - managed identity](prometheus-remote-write-managed-identity.md).
31+
- To configure remote-write to collect data from your self-managed Prometheus server, see [Azure Monitor managed service for Prometheus remote write](./remote-write-prometheus.md).
3232

3333
## Grafana integration
3434
The primary method for visualizing Prometheus metrics is [Azure Managed Grafana](../../managed-grafana/overview.md). [Connect your Azure Monitor workspace to a Grafana workspace](./azure-monitor-workspace-manage.md#link-a-grafana-workspace) so that it can be used as a data source in a Grafana dashboard. You then have access to multiple prebuilt dashboards that use Prometheus metrics and the ability to create any number of custom dashboards.

articles/azure-monitor/essentials/remote-write-prometheus.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,14 +11,14 @@ ms.date: 02/12/2024
1111
Azure Monitor managed service for Prometheus is intended to be a replacement for self-managed Prometheus so you don't need to manage a Prometheus server in your Kubernetes clusters. You may also choose to use the managed service to centralize data from self-managed Prometheus clusters for long term data retention and to create a centralized view across your clusters.
1212
In case you are using self-managed Prometheus, you can use [remote_write](https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage) to send data from your self-managed Prometheus into the Azure managed service.
1313

14-
For sending data from self-managed Prometheus running on your environments to Azure Monitor workspace, follow
14+
For sending data from self-managed Prometheus running on your environments to Azure Monitor workspace, follow the steps in this document.
1515

1616
## Choose the right solution for remote-write
1717

1818
Based on where your self-managed Prometheus is running, choose from the options below:
1919

2020
- **Self-managed Prometheus running on Azure Kubernetes Services (AKS) or Azure VM/VMSS**: Follow the steps in this documentation for configuring remote-write in Prometheus using User-assigned managed identity authentication.
21-
- **Self-managed Prometheus running on non-Azure environments**: Azure Monitor managed service for Prometheus has a managed offering for supported [Azure Arc-enabled Kubernetes](../../azure-arc/kubernetes/overview.md). However, if you wish to send data from self-managed Prometheus running on non-Azure or on-Prem environments, consider the following options:
21+
- **Self-managed Prometheus running on non-Azure environments**: Azure Monitor managed service for Prometheus has a managed offering for supported [Azure Arc-enabled Kubernetes](../../azure-arc/kubernetes/overview.md). However, if you wish to send data from self-managed Prometheus running on non-Azure or on-premises environments, consider the following options:
2222
- Onboard supported Kubernetes or VM/VMSS to [Azure Arc-enabled Kubernetes](../../azure-arc/kubernetes/overview.md) / [Azure Arc-enabled servers](../../azure-arc/servers/overview.md) which will allow you to manage and configure them in Azure. Then follow the steps in this documentation for configuring remote-write in Prometheus using User-assigned managed identity authentication.
2323
- For all other scenarios, follow the steps in this documentation for configuring remote-write in Prometheus using Azure Entra application.
2424

@@ -53,7 +53,7 @@ To send data to your Azure Monitor Workspace, you will need the following inform
5353
1. The managed identity must be assigned the **Monitoring Metrics Publisher** role on the data collection rule that is associated with your Azure Monitor Workspace.
5454
1. On the resource menu for your Azure Monitor workspace, select Overview. Select the link for Data collection rule:
5555

56-
:::image type="content" source="media/azure-monitor-workspace-overview/remote-write-dcr.png" lightbox="media/azure-monitor-workspace-overview/remote-write-dcr.png" alt-text="Screenshot of how to navigate to the data collection rule":::
56+
:::image type="content" source="media/azure-monitor-workspace-overview/remote-write-dcr.png" lightbox="media/azure-monitor-workspace-overview/remote-write-dcr.png" alt-text="Screenshot of how to navigate to the data collection rule.":::
5757

5858
1. On the resource menu for the data collection rule, select **Access control (IAM)**. Select Add, and then select Add role assignment.
5959
1. Select the **Monitoring Metrics Publisher role**, and then select **Next**.

articles/azure-monitor/toc.yml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -485,6 +485,9 @@ items:
485485
- name: Remote-write with Prometheus
486486
items:
487487
- name: Overview
488+
displayName: Prometheus,remote-write
489+
href: essentials/remote-write-prometheus.md
490+
- name: Remote-write using Azure Monitor sidecar
488491
displayName: Prometheus,remote-write
489492
href: containers/prometheus-remote-write.md
490493
- name: Microsoft Entra authorization proxy
@@ -889,6 +892,8 @@ items:
889892
href: essentials/prometheus-metrics-overview.md
890893
- name: FAQ
891894
href: essentials/prometheus-metrics-overview.md#frequently-asked-questions
895+
- name: Get started
896+
href: essentials/prometheus-get-started.md
892897
- name: Azure Monitor workspace
893898
items:
894899
- name: Overview
@@ -901,6 +906,9 @@ items:
901906
href: essentials/azure-monitor-workspace-private-endpoint.md
902907
- name: Private link for Prometheus data ingestion
903908
href: essentials/private-link-data-ingestion.md
909+
- name: Remote-write from self-managed Prometheus
910+
displayName: Prometheus
911+
href: essentials/remote-write-prometheus.md
904912
- name: Alerting and rule groups
905913
displayName: Prometheus
906914
href: essentials/prometheus-rule-groups.md

0 commit comments

Comments
 (0)