Skip to content

Commit 00e7023

Browse files
committed
new update
1 parent 2fe5fde commit 00e7023

File tree

2 files changed

+6
-15
lines changed

2 files changed

+6
-15
lines changed

docs/integrations/microsoft-azure/azure-virtual-network.md

Lines changed: 6 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -88,8 +88,7 @@ Azure service sends monitoring data to Azure Monitor, which can then [stream dat
8888

8989
* Virtual Network Flow Logs collection from Storage Account using our [Collect Logs from Azure Blob Storage](/docs/send-data/collect-from-other-data-sources/azure-blob-storage/block-blob/collect-logs) integration.
9090
* Activity Logs collection from [Azure Monitor](https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-get-started) using our [Azure Event Hubs source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/). It is recommended to create a separate source for activity logs. If you are already collecting these logs, you can skip this step.
91-
* Metrics collection using our [HTTP Logs and Metrics source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/) via Azure Functions deployed using the ARM template.
92-
91+
* Metrics collection using [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source).
9392

9493
You must explicitly enable diagnostic settings and network flow logs for each Virtual Network you want to monitor. You can forward metrics to the same event hub provided they satisfy the limitations and permissions as described [here](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/diagnostic-settings?tabs=portal#destination-limitations).
9594

@@ -300,16 +299,12 @@ import AppUninstall from '../../reuse/apps/app-uninstall.md';
300299

301300
## Troubleshooting
302301

303-
### App installation failed - Content Error - Invalid Field Extraction Rule
304-
305-
This error occurs if the app being installed attempts to create an FER by a name (AzureVirtualNetworkTargetResourceIdExtractionFER) which already exists in the org. This FER could have been created manually and is creating conflict with current app installation flow.
306-
307-
To resolve the issue, rename or delete the existing FER (AzureVirtualNetworkTargetResourceIdExtractionFER) and reinstall the app.
302+
### Metrics collection via Azure Metrics Source
308303

309-
### Metrics collection via the ARM template
304+
To troubleshoot metrics collection via Azure Metrics Source, follow the instructions in [Troubleshooting Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source/#troubleshooting).
310305

311-
To troubleshoot metrics collection via the ARM template, follow the instructions in [Collect Metrics from Azure Monitor > Troubleshooting metrics collection](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#troubleshooting-metrics-collection).
306+
### App installation failed - Content Error - Invalid Field Extraction Rule
312307

313-
### Metrics collection via Azure Metrics Source
308+
This error occurs if the app being installed attempts to create an FER by a name (AzureVirtualNetworkTargetResourceIdExtractionFER) which already exists in the org. This FER could have been created manually and is creating conflict with current app installation flow.
314309

315-
To troubleshoot metrics collection via Azure Metrics Source, follow the instructions in [Troubleshooting Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source/#troubleshooting).
310+
To resolve the issue, rename or delete the existing FER (AzureVirtualNetworkTargetResourceIdExtractionFER) and reinstall the app.

docs/integrations/microsoft-azure/kubernetes.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -400,10 +400,6 @@ import AppUninstall from '../../reuse/apps/app-uninstall.md';
400400

401401
## Troubleshooting
402402

403-
### Metrics collection via the ARM template
404-
405-
To troubleshoot metrics collection via the ARM template, follow the instructions in [Collect Metrics from Azure Monitor > Troubleshooting metrics collection](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#troubleshooting-metrics-collection).
406-
407403
### Metrics collection via Azure Metrics Source
408404

409405
To troubleshoot metrics collection via Azure Metrics Source, follow the instructions in [Troubleshooting Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source/#troubleshooting).

0 commit comments

Comments
 (0)