Skip to content

Commit 39eb82c

Browse files
flang-msftflang-msft
committed
added new file
1 parent 9864aaa commit 39eb82c

File tree

1 file changed

+129
-0
lines changed

1 file changed

+129
-0
lines changed

‎articles/partner-solutions/dynatrace/dynatrace-multiple-subscrptions.md

Lines changed: 129 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,129 @@
1+
---
2+
title: How to monitor multiple Dynatrace resources with Azure Native Dynatrace Service
3+
description: This article describes how to setup Dynatrace to monitor mulitple subscriptions using the Azure portal.
4+
5+
ms.topic: how-to
6+
ms.date: 08/27/2024
7+
8+
#CustomerIntent: As a web developer, I want use Dynatrace so that I can MSM.
9+
---
10+
You can now monitor all your subscriptions through a single Dynatrace resource using **Monitored Subscriptions**. Your experience is simplified because you don't have to set up a Dynatrace resource in every subscription that you intend to monitor. You can monitor multiple subscriptions by linking them to a single Dynatrace resource that is tied to a Dynatrace environment. This provides a single pane view for all resources across multiple subscriptions.
11+
12+
1. To manage multiple subscriptions that you want to monitor, select **Monitored Subscriptions** in the **Dynatrace environment configurations** section of the Resource menu.
13+
14+
<!-- ![](media/image1.png){width="6.5in" height="2.1666666666666665in"} -->
15+
16+
1. From **Monitored Subscriptions** in the Resource menu, select the **Add Subscriptions**. The **Add Subscriptions** experience that opens and shows the subscriptions you have *Owner* role assigned to and any Dynatrace resource created in those subscriptions that is already linked to the same Dynatrace environment as the current resource.
17+
18+
1. If the subscription you want to monitor has a resource already linked to the same Dynatrace org, we recommend that you delete the Dynatrace resources to avoid shipping duplicate data and incurring double the charges.
19+
20+
1. Select the subscriptions you want to monitor through the Dynatrace resource and select **Add**.
21+
22+
<!-- ![](media/image2.png){width="6.5in" height="3.375in"} -->
23+
24+
1. If the list doesn't get updated automatically, select **Refresh** to view the subscriptions and their monitoring status. You might see an intermediate status of *In Progress* while a subscription gets added. When the subscription is successfully added, you see the status is updated to **Active**. If a subscription fails to get added, **Monitoring Status** shows as **Failed**.
25+
26+
<!-- \<Screenshot TBD\> -->
27+
28+
The set of tag rules for metrics and logs defined for the Dynatrace resource applies to all subscriptions that are added for monitoring. Setting separate tag rules for different subscriptions isn\'t supported. Diagnostics settings are automatically added to resources in the added subscriptions that match the tag rules defined for the Dynatrace resource.
29+
30+
If you have existing Dynatrace resources that are linked to the account for monitoring, you can end up with duplication of logs that can result in added charges. Ensure you delete redundant Dynatrace resources that are already linked to the account. You can view the list of connected resources and delete the redundant ones. We recommend consolidating subscriptions into the same Dynatrace resource where possible.
31+
32+
<!-- 1. H1 -----------------------------------------------------------------------------
33+
34+
Required: Use a "<verb> * <noun>" format for your H1. Pick an H1 that clearly conveys the task the user will complete.
35+
36+
For example: "Migrate data from regular tables to ledger tables" or "Create a new Azure SQL Database".
37+
38+
* Include only a single H1 in the article.
39+
* Don't start with a gerund.
40+
* Don't include "Tutorial" in the H1.
41+
42+
-->
43+
44+
# "<verb> * <noun>"
45+
46+
TODO: Add your heading
47+
48+
<!-- 2. Introductory paragraph ----------------------------------------------------------
49+
50+
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.
51+
52+
Readers should have a clear idea of what they will do in this article after reading the introduction.
53+
54+
* Introduction immediately follows the H1 text.
55+
* Introduction section should be between 1-3 paragraphs.
56+
* Don't use a bulleted list of article H2 sections.
57+
58+
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.
59+
60+
-->
61+
62+
TODO: Add your introductory paragraph
63+
64+
<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info directly into the article text.
65+
66+
-->
67+
68+
<!-- 3. Prerequisites --------------------------------------------------------------------
69+
70+
Required: Make Prerequisites the first H2 after the H1.
71+
72+
* Provide a bulleted list of items that the user needs.
73+
* Omit any preliminary text to the list.
74+
* If there aren't any prerequisites, list "None" in plain text, not as a bulleted item.
75+
76+
-->
77+
78+
## Prerequisites
79+
80+
TODO: List the prerequisites
81+
82+
<!-- 4. Task H2s ------------------------------------------------------------------------------
83+
84+
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.
85+
86+
For portal-based procedures, minimize bullets and numbering.
87+
88+
* Each H2 should be a major step in the task.
89+
* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
90+
* Don't start with a gerund.
91+
* Don't number the H2s.
92+
* Begin each H2 with a brief explanation for context.
93+
* Provide a ordered list of procedural steps.
94+
* Provide a code block, diagram, or screenshot if appropriate
95+
* An image, code block, or other graphical element comes after numbered step it illustrates.
96+
* If necessary, optional groups of steps can be added into a section.
97+
* If necessary, alternative groups of steps can be added into a section.
98+
99+
-->
100+
101+
<!-- ## "\<verb\> * \<noun\>" -->
102+
103+
TODO: Add introduction sentence(s)
104+
[Include a sentence or two to explain only what is needed to complete the procedure.]
105+
TODO: Add ordered list of procedure steps
106+
107+
1. Step 1
108+
1. Step 2
109+
1. Step 3
110+
111+
112+
<!-- 5. Next step/Related content------------------------------------------------------------------------
113+
114+
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.
115+
- For Next step, provide one link to the next step in a sequence. Use the blue box format
116+
- 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.
117+
118+
-->
119+
120+
## Next steps
121+
122+
- [Manage the Dynatrace resource](dynatrace-how-to-manage.md)
123+
- Get started with Azure Native Dynatrace Service on
124+
125+
> [!div class="nextstepaction"]
126+
> [Azure portal](https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Dynatrace.Observability%2Fmonitors)
127+
128+
> [!div class="nextstepaction"]
129+
> [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/dynatrace.dynatrace_portal_integration?tab=Overview)

0 commit comments

Comments
 (0)