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
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.
58
58
59
59
## Configure scraping of Prometheus metrics
60
60
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.
62
62
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.
64
64
65
65
## Disable monitoring
66
66
@@ -72,21 +72,21 @@ helm del azmon-containers-release-1
72
72
73
73
## Update monitoring
74
74
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.
76
76
77
77
## After successful onboarding
78
78
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.
80
80
81
81
## Supported features
82
82
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).
0 commit comments