Skip to content

Commit d8fa6ec

Browse files
author
Sakthi Vetrivel
committed
fixing links
1 parent 6d697c4 commit d8fa6ec

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

articles/openshift/howto-azure-monitor-v4.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -40,27 +40,27 @@ This article describes how to enable the private preview of Azure Monitor for co
4040
curl -LO https://raw.githubusercontent.com/microsoft/OMS-docker/ci_feature/docs/openshiftV4/onboarding_azuremonitor_for_containers.sh
4141
```
4242

43-
Execute below script with azureSubscriptionId, workspace Region, clusterName, and context of the Kubernetes cluster.
43+
Execute the following script with azureSubscriptionId, workspace Region, clusterName, and context of the Kubernetes cluster.
4444

4545
```bash
4646
bash onboarding_azuremonitor_for_containers.sh <azureSubscriptionId> <azureRegionforLogAnalyticsWorkspace> <clusterName> <kubeconfigContextNameOftheCluster>
4747
```
4848

49-
For Example:
49+
For example:
5050

5151
```bash
5252
bash onboarding_azuremonitor_for_containers.sh 27ac26cf-a9f0-4908-b300-9a4e9a0fb205 eastus myocp42 admin
5353
```
5454

5555
## Configure agent data collection
5656

57-
By default, Monitoring Agent collects the {stdout; stderr} container logs of all the containers running in all the namespaces except kube-system. If you want to configure the container log collection specific to particular namespace or namespaces, you can refer to [Container Insights agent configuration](../azure-monitor/insights/container-insights-agent-config). Here, you can configure Monitoring agent with desired data collection settings using config map.
57+
By default, Monitoring Agent collects the {stdout; stderr} container logs of all the containers running in all the namespaces except kube-system. If you want to configure the container log collection specific to particular namespace or namespaces, you can refer to [Container Insights agent configuration](../azure-monitor/insights/container-insights-agent-config.md). Here, you can configure Monitoring agent with desired data collection settings using config map.
5858

5959
## Configure scraping of Prometheus metrics
6060

61-
Azure Monitor for containers scrapes the Prometheus metrics and ingest to the Azure Monitor backend. Refer to [Container Insights Prometheus configuration](../azure-monitor/insights/container-insights-prometheus-integration) for the instructions how to configure Prometheus scraping.
61+
Azure Monitor for containers scrapes the Prometheus metrics and ingest to the Azure Monitor backend. Refer to [Container Insights Prometheus configuration](../azure-monitor/insights/container-insights-prometheus-integration.md) for the instructions how to configure Prometheus scraping.
6262

63-
After successful onboarding, navigate to https://aka.ms/azmon-containers-hybrid and select Environment as **"All"** to view your newly onboarded OpenShift v4 cluster.
63+
After successful onboarding, navigate to [Hybrid Monitoring](https://aka.ms/azmon-containers-hybrid) and select Environment as **"All"** to view your newly onboarded OpenShift v4 cluster.
6464

6565
## Disable monitoring
6666

@@ -72,21 +72,21 @@ helm del azmon-containers-release-1
7272

7373
## Update monitoring
7474

75-
Rerun the onboarding script as described in the [Onboarding](#onboarding) section with the same parameter to get updated to latest Helm chart.
75+
Rerun the onboarding script as described in the [Onboarding](#onboarding) section with the same parameter to update to latest Helm chart.
7676

7777
## After successful onboarding
7878

79-
Navigate to [Hybrid Monitoring](https://aka.ms/azmon-containers-hybrid) and you should be able to see your newly enabled OpenShift/ARO v4 cluster with health status in the **Monitored Clusters** tab and you can get into deeper insights such as metrics, inventory, and logs and more by clicking the **Cluster** column.
79+
Navigate to [Hybrid Monitoring](https://aka.ms/azmon-containers-hybrid), and you can see your newly enabled OpenShift/ARO v4 cluster with health status in the **Monitored Clusters** tab. There, you can get into deeper insights such as metrics, inventory, and logs by clicking the **Cluster** column.
8080

8181
## Supported features
8282

83-
For more information, see [Container Insights overview](../azure-monitor/insights/container-insights-overview) for more details on the supported features and functionality.
83+
For more on the supported features and functionality, see [Container Insights overview](../azure-monitor/insights/container-insights-overview.md).
8484

85-
Contact us via [email protected] the feedback and questions.
85+
Contact us via [email protected] for feedback and questions.
8686

8787
## Next steps
8888

8989
To learn more about monitoring, see:
90-
../azure/azure-monitor/insights/container-insights-overview
90+
- [Container Insights overview](../azure/azure-monitor/insights/container-insights-overview.md)
9191

92-
../azure/azure-monitor/log-query/log-query-overview
92+
- [Log Query overview](../azure/azure-monitor/log-query/log-query-overview.md)

0 commit comments

Comments
 (0)