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/monitor-private-5g-core-alerts.md
+3-87Lines changed: 3 additions & 87 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,88 +7,16 @@ ms.service: private-5g-core
7
7
ms.topic: how-to
8
8
ms.date: 09/14/2023
9
9
10
-
#CustomerIntent: As a < type of user >, I want < what? > so that < why? >.
11
10
---
12
-
13
-
<!--
14
-
Remove all the comments in this template before you sign-off or merge to the main branch.
15
-
16
-
This template provides the basic structure of a How-to article pattern. See the
17
-
[instructions - How-to](../level4/article-how-to-guide.md) in the pattern library.
18
-
19
-
You can provide feedback about this template at: https://aka.ms/patterns-feedback
20
-
21
-
How-to is a procedure-based article pattern that show the user how to complete a task in their own environment. A task is a work activity that has a definite beginning and ending, is observable, consist of two or more definite steps, and leads to a product, service, or decision.
Required: Lead with a light intro that describes, in customer-friendly language, what the customer will do. Answer the fundamental “why would I want to do this?” question. Keep it short.
41
-
42
-
Readers should have a clear idea of what they will do in this article after reading the introduction.
43
-
44
-
* Introduction immediately follows the H1 text.
45
-
* Introduction section should be between 1-3 paragraphs.
46
-
* Don't use a bulleted list of article H2 sections.
47
-
48
-
Example: In this article, you will migrate your user databases from IBM Db2 to SQL Server by using SQL Server Migration Assistant (SSMA) for Db2.
49
-
50
-
-->
51
-
52
13
Alerts help track important events in your network by notifying you with an email containing diagnostic information when certain, user-defined conditions are met. Alerts can be customized to represent the severity of incidents on your network and can be viewed in the [Monitor service under Azure Services(https://portal.azure.com/#view/Microsoft_Azure_Monitoring/AzureMonitoringBrowseBlade/~/overview)]. In this how-to guide, you will create a custom alert for a packet core control plane or data plane.
53
14
54
-
<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info directly into the article text.
Required: Make Prerequisites the first H2 after the H1.
61
-
62
-
* Provide a bulleted list of items that the user needs.
63
-
* Omit any preliminary text to the list.
64
-
* If there aren't any prerequisites, list "None" in plain text, not as a bulleted item.
65
-
66
-
-->
67
-
68
15
## Prerequisites
69
16
70
17
1. Ensure you can sign in to the Azure portal using an account with access to the active subscription you used to create your private mobile network. This account must have the build-in Contributor or Owner role at the subscription scope.
71
18
1. You must have [deployed your private mobile network](how-to-guide-deploy-a-private-mobile-network-azure-portal.md).
Required: Multiple procedures should be organized in H2 level sections. A section contains a major grouping of steps that help users complete a task. Each section is represented as an H2 in the article.
76
-
77
-
For portal-based procedures, minimize bullets and numbering.
78
-
79
-
* Each H2 should be a major step in the task.
80
-
* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
81
-
* Don't start with a gerund.
82
-
* Don't number the H2s.
83
-
* Begin each H2 with a brief explanation for context.
84
-
* Provide a ordered list of procedural steps.
85
-
* Provide a code block, diagram, or screenshot if appropriate
86
-
* An image, code block, or other graphical element comes after numbered step it illustrates.
87
-
* If necessary, optional groups of steps can be added into a section.
88
-
* If necessary, alternative groups of steps can be added into a section.
89
-
90
-
-->
91
-
92
20
## Create an alert rule for your packet core control/data plane
93
21
94
22
1. Navigate to the packet core control/data plane you want to create an alert for.
@@ -97,28 +25,16 @@ For portal-based procedures, minimize bullets and numbering.
97
25
98
26
1. Select **Alerts** from the **Monitoring** tab on the resource menu.
1. Select **Alert Rule** from the **Create** dropdown at the top of the page.
103
31
104
-
:::image type="content" source="media/alert2.png" alt-text="Screenshot of Azure portal showing alerts menu with the create dropdown menu open.":::
32
+
:::image type="content" source="media/alerts-create-dropdown.png" alt-text="Screenshot of Azure portal showing alerts menu with the create dropdown menu open.":::
105
33
106
34
1. Select **See all signals** just under the dropdown menu or from inside the dropdown menu.
107
35
108
-
:::image type="content" source="media/alert3.png" alt-text="Screenshot of Azure portal showing alert signal selection menu." lightbox="media/alert3.png":::
36
+
:::image type="content" source="media/packet-core-alerts-signal-list.png" alt-text="Screenshot of Azure portal showing alert signal selection menu." lightbox="media/alert3.png":::
109
37
110
38
1. Select the signal you want the alert to be based on and follow the rest of the create instructions.
111
39
1. Once you've reached the end of the create instructions, select **Review + create** to create your alert.
112
40
1. Verify that your alert rule was created by navigating to the alerts page for your packet core (see steps 1 and 2) and finding it in the list of alert rules on the page.
113
-
114
-
<!-- 5. Next step/Related content------------------------------------------------------------------------
115
-
116
-
Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
117
-
- For Next step, provide one link to the next step in a sequence. Use the blue box format
118
-
- For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
119
-
120
-
-->
121
-
122
-
<!--
123
-
Remove all the comments in this template before you sign-off or merge to the main branch.
0 commit comments