Skip to content

Commit acd3204

Browse files
authored
Update azure-public-ipAddress.md
1 parent 49122ca commit acd3204

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/integrations/microsoft-azure/azure-public-ipAddress.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
88

99
<img src={useBaseUrl('img/integrations/microsoft-azure/azure-public-ipAddress.png')} alt="Thumbnail icon" width="50"/>
1010

11-
[Azure Public IP Addresses](https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-addresses) are used by internet resources to communicate inbound to resources in Azure. A public IP address is a resource with its own properties and can be associated with other azure resources like NAT gateways, Application gateways etc. This integration helps in monitoring DDoS notification events, packet dropped rate, TCP, and UDP data throughput.
11+
[Azure Public IP Addresses](https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-addresses) are used by internet resources to communicate inbound to resources in Azure. A public IP address is a resource with its own properties and can be associated with other Azure resources like NAT gateways, Application gateways, and more. This integration helps in monitoring DDoS notification events, packet dropped rate, TCP, and UDP data throughput.
1212

1313
## Log and metric types
1414

@@ -31,25 +31,25 @@ When you configure the event hubs source or HTTP source, plan your source catego
3131

3232
### Configure metrics collection
3333

34-
In this section, you will configure a pipeline for shipping metrics from Azure Monitor to an Event Hub, on to an Azure Function, and finally to an HTTP Source on a hosted collector in Sumo Logic.
34+
In this section, you will configure a pipeline for shipping metrics from Azure Monitor to an Event Hub, onto an Azure Function, and finally to an HTTP Source on a hosted collector in Sumo Logic.
3535

3636
1. Create a hosted collector and tag the `tenant_name` field. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name). <br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Tenant-Name.png')} alt="Azure Tag Tenant Name" style={{border: '1px solid gray'}} width="500" />
3737
1. [Configure an HTTP Source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-1-configure-an-http-source).
3838
1. [Configure and deploy the ARM Template](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-2-configure-azure-resources-using-arm-template).
39-
1. [Export metrics to Event Hub](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-3-export-metrics-for-a-particular-resource-to-event-hub). Perform below steps for each Public IP resource that you want to monitor.
40-
* Choose `Stream to an event hub` as destination.
39+
1. [Export metrics to Event Hub](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-3-export-metrics-for-a-particular-resource-to-event-hub). Perform the steps below for each Public IP resource that you want to monitor.
40+
* Choose `Stream to an event hub` as the destination.
4141
* Select `AllMetrics`.
42-
* Use the Event hub namespace created by the ARM template in Step 2 above. You can create a new Event hub or use the one created by ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name.
42+
* Use the Event hub namespace created by the ARM template in Step 2 above. You can create a new Event hub or use the one created by the ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name.
4343

4444
### Configure logs collection
4545

4646
In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.
4747

4848
1. To set up the Azure Event Hubs source in Sumo Logic, refer to [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
49-
2. To create the Diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/monitor-public-ip#creating-a-diagnostic-setting). Perform below steps for each Public IP resource that you want to monitor.
49+
2. To create the Diagnostic settings in the Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/monitor-public-ip#creating-a-diagnostic-setting). Perform the steps below for each Public IP resource that you want to monitor.
5050
* Choose `Stream to an event hub` as the destination.
5151
* Select `allLogs`.
52-
* Use the Event hub namespace and Event hub name configured in previous step in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
52+
* Use the Event hub namespace and Event hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
5353

5454
## Troubleshooting
5555

0 commit comments

Comments
 (0)