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
- Raising Acrolinx score for faq.yml.
- Please note that Acrolinx incorrectly flags a number of code samples and error messages as Correctness issues. We cannot do anything about that.
Copy file name to clipboardExpand all lines: articles/azure-monitor/faq.yml
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ sections:
87
87
- question: |
88
88
Why am I seeing duplicate records in Azure Monitor Logs?
89
89
answer: |
90
-
You may on occasion notice duplicate records in Azure Monitor Logs. This will typically be from one of the following two conditions.
90
+
You may on occasion notice duplicate records in Azure Monitor Logs. This duplication is typically from one of the following two conditions.
91
91
92
92
- Components in the pipeline have retries to ensure reliable delivery at the destination. Occasionally, this capability may result in duplicates for a small percentage of telemetry items.
93
93
- If the duplicate records come from a virtual machine, then you may have both the Log Analytics agent and Azure Monitor agent installed. If you still need the Log Analytics agent installed, then configure the Log Analytics workspace to no longer collect data that’s also being collected by the data collection rule used by Azure Monitor agent.
@@ -196,7 +196,7 @@ sections:
196
196
- question: |
197
197
What is an action rule?
198
198
answer: |
199
-
An action rule allows you to modify the behavior of a set of alerts that match a certain criteria. This allows you to perform such requirements as disable alert actions during a maintenance window. You can also apply an action group to a set of alerts rather than applying them directly to the alert rules. See [Action rules](alerts/alerts-action-rules.md).
199
+
An action rule allows you to modify the behavior of a set of alerts that match a certain criteria. This rule allows you to perform such requirements as disable alert actions during a maintenance window. You can also apply an action group to a set of alerts rather than applying them directly to the alert rules. See [Action rules](alerts/alerts-action-rules.md).
200
200
201
201
- name: Agents
202
202
questions:
@@ -297,8 +297,8 @@ sections:
297
297
What's the upgrade path from Log Analytics Agent (MMA) to Azure Monitor Agent (AMA) for monitoring System Center Operations Manager? Can we use AMA for System Center Operations Manager scenarios?
298
298
answer: |
299
299
Here's how AMA impacts the two System Center Operations Manager related monitor scenarios:
300
-
- **Scenario 1**: For monitoring the Windows operating system of System Center Operations Manager, the upgrade path is same as any other machine, wherein you can migrate from MMA (versions 2016, 2019) to AMA as soon as your required parity features are available on AMA.
301
-
- **Scenario 2**: For onboarding/connecting System Center Operations Manager to Log Analytics workspaces, since this is enabled via a System Center Operations Manager connector for Log Analytics/Azure Monitor, neither MMA nor AMA is required to be installed on the Operations Manager management server. As such, there's no impact to this use case from AMA perspective.
300
+
- **Scenario 1**: Monitoring the Windows operating system of System Center Operations Manager. The upgrade path is same as any other machine, wherein you can migrate from MMA (versions 2016, 2019) to AMA as soon as your required parity features are available on AMA.
301
+
- **Scenario 2**: Onboarding/connecting System Center Operations Manager to Log Analytics workspaces. This is enabled via a System Center Operations Manager connector for Log Analytics/Azure Monitor, neither MMA nor AMA is required to be installed on the Operations Manager management server. As such, there's no impact to this use case from AMA perspective.
302
302
303
303
304
304
- question: |
@@ -804,7 +804,7 @@ sections:
804
804
805
805
However, there are still cases where even when server-side monitoring is enabled on an application's web server that a 502 or 503 error will not be captured by Application Insights. Many modern web servers do not allow a client to communicate directly, but instead employ solutions like reverse proxies to pass information back and forth between the client and the front-end web servers.
806
806
807
-
In this scenario, a 502 or 503 response could be returned to a client due to an issue at the reverse proxy layer and would not be captured out-of-box by Application Insights. To help detect issues at this layer you may need to forward logs from your reverse proxy to Log Analytics and create a custom rule to check for 502/503 responses. To learn more about common causes of 502 and 503 errors consult the Azure App Service [troubleshooting article for "502 bad gateway" and "503 service unavailable"](../app-service/troubleshoot-http-502-http-503.md).
807
+
In this scenario, a 502 or 503 response could be returned to a client due to an issue at the reverse proxy layer and would not be captured out-of-box by Application Insights. To help detect issues at this layer, you may need to forward logs from your reverse proxy to Log Analytics and create a custom rule to check for 502/503 responses. To learn more about common causes of 502 and 503 errors consult the Azure App Service [troubleshooting article for "502 bad gateway" and "503 service unavailable"](../app-service/troubleshoot-http-502-http-503.md).
808
808
809
809
- name: OpenTelemetry
810
810
questions:
@@ -848,7 +848,7 @@ sections:
848
848
You can see our progress toward OpenTelemetry-Based Azure Monitor exporters for [C#](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/monitor/Azure.Monitor.OpenTelemetry.Exporter), [JavaScript](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/monitor/monitor-opentelemetry-exporter), and [Python](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/monitor/azure-monitor-opentelemetry-exporter/) in open-source repositories.
Is running Application Insights alongside competitor agents supported? (for example, AppDynamics, DataDog, NewRelic, etc.)
852
852
answer: |
853
853
No. This isn't something we plan to test or support, though our OpenTelemetry-based offerings allow you to [export to an OTLP endpoint](app/opentelemetry-enable.md#enable-the-otlp-exporter) alongside Azure Monitor simultaneously.
854
854
@@ -1065,7 +1065,7 @@ sections:
1065
1065
- question: |
1066
1066
Why did my VM fail to onboard?
1067
1067
answer: |
1068
-
When onboarding an Azure VM from the Azure portal, the following steps occur:
1068
+
The following steps occur onboarding an Azure VM from the Azure portal:
1069
1069
1070
1070
* A default Log Analytics workspace is created, if that option was selected.
1071
1071
* The Log Analytics agent is installed on Azure VMs using a VM extension, if determined it's required.
0 commit comments