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/private-5g-core/gather-diagnostics.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,9 @@ You must already have an AP5GC site deployed to collect diagnostics.
63
63
1. Select **Diagnostics collection**.
64
64
1. AP5GC online service will generate a package and upload it to the provided storage account URL. Once AP5GC reports that the upload has succeeded, report the SAS URL to Azure support.
65
65
1. Generate a SAS URL by selecting **Generate SAS** on the blob details blade.
66
-
1. Copy the contents of the **Blob SAS URL** field and share the URL with your support representative.
66
+
1. Copy the contents of the **Blob SAS URL** field and share the URL with your support representative via a [support request ticket](/azure/azure-portal/supportability/how-to-create-azure-support-request).
67
+
> [!IMPORTANT]
68
+
> You must always set **Service type** to **Azure Private 5G Core** when raising a support request for any issues related to AP5GC.
67
69
1. Azure support will access the diagnostics using the provided SAS URL and provide support based on the information.
68
70
69
71
## Troubleshooting
@@ -72,7 +74,9 @@ You must already have an AP5GC site deployed to collect diagnostics.
72
74
- If an invalid container URL was passed, the request will be rejected and report **400 Bad Request**. Repeat the process with the correct container URL.
73
75
- If the asynchronous part of the operation fails, the asynchronous operation resource is set to **Failed** and reports a failure reason.
74
76
- Additionally, check that the same user-assigned identity was added to both the site and storage account.
75
-
- If this does not resolve the issue, share the correlation ID of the failed request with AP5GC support for investigation.
77
+
- If this does not resolve the issue, share the correlation ID of the failed request with AP5GC support for investigation via a [support request ticket](/azure/azure-portal/supportability/how-to-create-azure-support-request).
78
+
> [!IMPORTANT]
79
+
> You must always set **Service type** to **Azure Private 5G Core** when raising a support request for any issues related to AP5GC.
0 commit comments