Skip to content

Commit e016e95

Browse files
Make UE usage preview only
1 parent 64aa683 commit e016e95

7 files changed

+9
-17
lines changed

articles/private-5g-core/collect-required-information-for-a-site.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -61,12 +61,6 @@ Collect all the values in the following table to define the packet core instance
6161
| The virtual network name on port 5 on your Azure Stack Edge Pro device corresponding to the control plane interface on the access network. For 5G, this interface is the N2 interface; for 4G, it's the S1-MME interface. | **ASE N2 virtual subnet** (for 5G) or **ASE S1-MME virtual subnet** (for 4G). |
6262
| The virtual network name on port 5 on your Azure Stack Edge Pro device corresponding to the user plane interface on the access network. For 5G, this interface is the N3 interface; for 4G, it's the S1-U interface. | **ASE N3 virtual subnet** (for 5G) or **ASE S1-U virtual subnet** (for 4G). |
6363

64-
## Collect UE usage tracking values
65-
66-
You can optionally track UE usage for with Azure Event Hubs. If you want to track UE usage, you must already have an Azure Event Hub created. If you do not already have an Azure Event Hub, see [Quickstart: Create an event hub using Azure portal](/azure/event-hubs/event-hubs-create) for how to create one.
67-
68-
If you want to enable Event Hub UE usage tracking, [collect the connection string from your Azure Event Hub](/azure/event-hubs/event-hubs-get-connection-string#connection-string-for-a-specific-event-hub-in-a-namespace). This string is required as input for the **Event hub connection string** field in the Azure portal.
69-
7064
## Collect data network values
7165

7266
You can configure up to three data networks per site. During site creation, you'll be able to choose whether to attach an existing data network or create a new one.

articles/private-5g-core/create-additional-packet-core.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -45,9 +45,6 @@ In this step, you'll create an additional packet core instance for a site in you
4545
> [!NOTE]
4646
> **ASE N2 virtual subnet** and **ASE N3 virtual subnet** (if this site supports 5G UEs) or **ASE S1-MME virtual subnet** and **ASE S1-U virtual subnet** (if this site supports 4G UEs) must match the corresponding virtual network names on port 5 on your Azure Stack Edge Pro device.
4747
48-
1. If you want to configure **UE usage tracking**:
49-
1. Set **UE metric monitoring** to **Enabled**.
50-
1. Use the information you collected in [Collect UE usage tracking values](collect-required-information-for-a-site.md#collect-ue-usage-tracking-values) to configure the **Event hub connection string**.
5148
1. In the **Attached data networks** section, select **Attach data network**. Select the existing data network you used for the site then use the information you collected in [Collect data network values](collect-required-information-for-a-site.md#collect-data-network-values) to fill out the fields. Note the following:
5249
- **ASE N6 virtual subnet** (if this site supports 5G UEs) or **ASE SGi virtual subnet** (if this site supports 4G UEs) must match the corresponding virtual network name on port 6 on your Azure Stack Edge Pro device.
5350
- If you decided not to configure a DNS server, clear the **Specify DNS addresses for UEs?** checkbox.

articles/private-5g-core/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ landingContent:
144144
url: distributed-tracing.md
145145
- text: Local monitoring with packet core dashboards
146146
url: packet-core-dashboards.md
147-
- text: Monitor AP5GC UE usage with Event Hubs
147+
- text: Monitor AP5GC UE usage with Event Hubs (Preview)
148148
url: ue-usage-event-hub.md
149149
- linkListType: how-to-guide
150150
links:

articles/private-5g-core/modify-packet-core.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -92,9 +92,6 @@ To modify the packet core and/or access network configuration:
9292

9393
- Use the information you collected in [Collect packet core configuration values](collect-required-information-for-a-site.md#collect-packet-core-configuration-values) for the top-level configuration values.
9494
- Use the information you collected in [Collect access network values](collect-required-information-for-a-site.md#collect-access-network-values) for the configuration values under **Access network**.
95-
- If you want to configure **UE usage tracking**:
96-
1. Set **UE metric monitoring** to **Enabled**.
97-
1. Use the information you collected in [Collect UE usage tracking values](collect-required-information-for-a-site.md#collect-ue-usage-tracking-values) to configure the **Event hub connection string**.
9895
1. Choose the next step:
9996
- If you've finished modifying the packet core instance, go to [Submit and verify changes](#submit-and-verify-changes).
10097
- If you want to configure a new or existing data network and attach it to the packet core instance, go to [Attach a data network](#attach-a-data-network).

articles/private-5g-core/monitor-private-5g-core-with-platform-metrics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,4 +63,4 @@ See [Supported metrics with Azure Monitor](/azure/azure-monitor/essentials/metri
6363
## Next steps
6464

6565
- [Learn more about the Azure Monitor Metrics](/azure/azure-monitor/essentials/data-platform-metrics)
66-
- [Monitor UE usage via Azure Event Hub](/azure/event-hubs/monitor-event-hubs)
66+
- [Monitor UE usage via Azure Event Hubs (Preview)](/azure/event-hubs/monitor-event-hubs)

articles/private-5g-core/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ items:
5858
href: distributed-tracing.md
5959
- name: Local monitoring with packet core dashboards
6060
href: packet-core-dashboards.md
61-
- name: Monitoring UE usage with Event Hubs
61+
- name: Monitoring UE usage with Event Hubs (Preview)
6262
href: ue-usage-event-hub.md
6363
- name: Reliability
6464
href: reliability-private-5g-core.md

articles/private-5g-core/ue-usage-event-hub.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Monitor UE usage with Event Hubs
2+
title: Monitor UE usage with Event Hubs (Preview)
33
description: Information on using Azure Event Hubs to monitor UE usage in your private mobile network.
44
author: robswain
55
ms.author: robswain
@@ -15,7 +15,11 @@ Azure Private 5G Core can be configured to integrate with [Event Hubs](/azure/ev
1515

1616
You can [monitor UE usage](/azure/event-hubs/monitor-event-hubs) based on the monitoring data generated by Azure Event Hubs, and analyze or alert on this data with [Azure Monitor](/azure/azure-monitor/overview).
1717

18-
UE usage monitoring can be configured during site creation - see [Collect UE usage tracking values](collect-required-information-for-a-site.md#collect-ue-usage-tracking-values) - or at a later stage by [modifying the packet core](modify-packet-core.md). Once configured for the site, you must add the [UE usage schema](#ue-usage-schema) to a Schema Registry in order to use monitor UE usage in your deployment - see [Azure Schema Registry in Azure Event Hubs](/azure/event-hubs/schema-registry-overview).
18+
## Configure UE usage monitoring
19+
20+
UE usage monitoring can be configured during site creation or at a later stage. If you want to configure UE usage monitoring for a site, please contact your support representative.
21+
22+
Once configured for the site, you must add the [UE usage schema](#ue-usage-schema) to a Schema Registry in order to use monitor UE usage in your deployment - see [Azure Schema Registry in Azure Event Hubs](/azure/event-hubs/schema-registry-overview).
1923

2024
## Reported UE usage data
2125

0 commit comments

Comments
 (0)