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/azure-monitor/faq.yml
+4-14Lines changed: 4 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ metadata:
11
11
ms.date: 10/24/2022
12
12
title: Azure Monitor Frequently Asked Questions
13
13
summary: |
14
-
This Microsoft FAQ is a list of commonly asked questions about Azure Monitor. If you have any other questions, go to the [discussion forum](/answers/questions/topics/single/24223.html) and post your questions. When a question is frequently asked, we add it to this article so that it can be found quickly and easily.
14
+
This Microsoft FAQ is a list of commonly asked questions about Azure Monitor.
15
15
16
16
17
17
sections:
@@ -221,7 +221,7 @@ sections:
221
221
- question: |
222
222
I see some gaps in metric data, why is this occurring?
223
223
answer: |
224
-
During node updates you may see a 1 to 2 minute gap in metric data for metrics collected from our cluster level collectors because the node that it runs on is being updated as part of a normal update process. This affects cluster-wide targets such as kube-state-metrics and custom application targets that are specified. This occurs when your cluster is updated manually or via auto-update. This is expected behavior that occurs due to the node it runs on being updated. None of our recommended alert rules are affected by this behavior.
224
+
During node updates you might see a 1 to 2 minute gap in metric data for metrics collected from our cluster level collectors because the node that it runs on is being updated as part of a normal update process. This affects cluster-wide targets such as kube-state-metrics and custom application targets that are specified. This occurs when your cluster is updated manually or via auto-update. This is expected behavior that occurs due to the node it runs on being updated. None of our recommended alert rules are affected by this behavior.
225
225
226
226
- name: Change Analysis
227
227
questions:
@@ -595,7 +595,7 @@ sections:
595
595
- question: |
596
596
Can I use the Azure Monitor Exporter as a standalone component?
597
597
answer: |
598
-
Yes, we understand some customers may want to instrument using a "piecemeal approach". However, the distro provides easiest way to get started with the best experience on Azure.
598
+
Yes, we understand some customers might want to instrument using a "piecemeal approach". However, the distro provides easiest way to get started with the best experience on Azure.
599
599
600
600
- question: |
601
601
What's the difference between manual and auto-instrumentation?
@@ -620,7 +620,7 @@ sections:
620
620
- question: |
621
621
Why do I see info banner "You do not have the right cluster permissions which will restrict your access to Container Insights features. Please reach out to your cluster admin to get the right permission"?
622
622
answer: |
623
-
Container Insights has historically allowed users to access the Azure portal experience based on the access permission of the Log Analytics workspace. It now checks cluster-level permission to provide access to the Azure portal experience. You may need your cluster admin to assign this permission.
623
+
Container Insights has historically allowed users to access the Azure portal experience based on the access permission of the Log Analytics workspace. It now checks cluster-level permission to provide access to the Azure portal experience. You might need your cluster admin to assign this permission.
624
624
625
625
For basic read-only cluster level access, assign the **Monitoring Reader** role for the following types of clusters.
626
626
@@ -935,13 +935,3 @@ sections:
935
935
answer: |
936
936
The frequency of data collection is customizable. See [Data collected by SQL Insights (preview)](/azure/azure-sql/database/sql-insights-overview#collected-data) for information on the default frequencies. See [Create SQL monitoring profile](/azure/azure-sql/database/sql-insights-enable#create-sql-monitoring-profile) for instructions on customizing frequencies.
937
937
938
-
additionalContent: |
939
-
940
-
## Next steps
941
-
942
-
If your question isn't answered here, see more questions and answers at the following forums:
0 commit comments