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
Copy file name to clipboardExpand all lines: articles/aks/open-service-mesh-open-source-observability.md
+8-22Lines changed: 8 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,10 +28,10 @@ In this tutorial, you will:
28
28
> [!div class="checklist"]
29
29
>
30
30
> - Create and deploy a Prometheus instance
31
-
> - Configure OSM to allow Prometheus scraping
32
31
> - Update the Prometheus `Configmap`
33
32
> - Create and deploy a Grafana instance
34
33
> - Configure Grafana with the Prometheus datasource
34
+
> - Enable Prometheus metrics for a user namespace
35
35
> - Import OSM dashboard for Grafana
36
36
> - Create and deploy a Jaeger instance
37
37
> - Configure Jaeger tracing for OSM
@@ -100,29 +100,9 @@ For more information on running Prometheus, visit:
100
100
https://prometheus.io/
101
101
```
102
102
103
-
### Configure OSM to allow Prometheus scraping
104
-
105
-
To ensure that the OSM components are configured for Prometheus scrapes, we'll want to check the **prometheus_scraping** configuration located in the osm-config config file. View the configuration with the following command:
The output of the previous command should return `true` if OSM is configured for Prometheus scraping. If the returned value is `false`, we will need to update the configuration to be `true`. Run the following command to turn **on** OSM Prometheus scraping:
The default installation of Prometheus will contain two Kubernetes `configmaps`. You can view the list of Prometheus `configmaps` with the following command.
105
+
By default, Prometheus is set to scrape the OSM components. The default installation of Prometheus will contain two Kubernetes `configmaps`. You can view the list of Prometheus `configmaps` with the following command.
126
106
127
107
```azurecli-interactive
128
108
kubectl get configmap | grep prometheus
@@ -452,6 +432,12 @@ Click the **Add data source** button and select Prometheus under time series dat
452
432
453
433
On the **Configure your Prometheus data source below** page, enter the Kubernetes cluster FQDN for the Prometheus service for the HTTP URL setting. The default FQDN should be `stable-prometheus-server.default.svc.cluster.local`. Once you have entered that Prometheus service endpoint, scroll to the bottom of the page and select **Save & Test**. You should receive a green checkbox indicating the data source is working.
454
434
435
+
### Enable Prometheus metrics for a user namespace
436
+
In order to configure Prometheus to scrape metrics from an application namespace, run the following command.
0 commit comments