Skip to content

Commit 8dd7bdf

Browse files
Merge pull request #290125 from ProfessorKendrick/liftr-edit-dynatrace
[Liftr] user story 29035005
2 parents 4c18133 + d1988ea commit 8dd7bdf

File tree

1 file changed

+7
-31
lines changed

1 file changed

+7
-31
lines changed

articles/partner-solutions/dynatrace/dynatrace-how-to-manage.md

Lines changed: 7 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Manage your Azure Native Dynatrace Service integration
33
description: This article describes how to manage Dynatrace on the Azure portal.
44

55
ms.topic: conceptual
6-
ms.date: 08/28/2024
6+
ms.date: 11/07/2024
77

88
---
99

@@ -29,7 +29,7 @@ The details include:
2929

3030
At the bottom, you see two tabs:
3131

32-
- **Get started tab** also provides links to Dynatrace dashboards, logs and Smartscape Topology.
32+
- **Get started tab** also provides links to Dynatrace dashboards, logs, and Smartscape Topology.
3333
- **Monitoring tab** provides a summary of the resources sending logs to Dynatrace.
3434

3535
If you select the **Monitoring** pane, you see a table with information about the Azure resources sending logs to Dynatrace.
@@ -62,34 +62,10 @@ The column **Logs to Dynatrace** indicates whether the resource is sending logs
6262

6363
- _Resource doesn't support sending logs_ - Only resource types with monitoring log categories can be configured to send logs. See [supported categories](/azure/azure-monitor/essentials/resource-logs-categories).
6464
- _Limit of five diagnostic settings reached_ - Each Azure resource can have a maximum of five diagnostic settings. For more information, see [diagnostic settings](/cli/azure/monitor/diagnostic-settings).
65-
- _Error_ - The resource is configured to send logs to Dynatrace, but is blocked by an error.
65+
- _Error_ - The resource is configured to send logs to Dynatrace, but is blocked due to an error.
6666
- _Logs not configured_ - Only Azure resources that have the appropriate resource tags are configured to send logs to Dynatrace.
6767
- _Agent not configured_ - Virtual machines without the Dynatrace OneAgent installed don't emit logs to Dynatrace.
6868

69-
## Use one Dynatrace resource with multiple subscriptions
70-
71-
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.
72-
73-
To manage multiple subscriptions that you want to monitor, select **Monitored Subscriptions** in the **Dynatrace environment configurations** section of the Resource menu.
74-
75-
:::image type="content" source="media/dynatrace-how-to-manage/dynatrace-monitored-subscriptions.png" alt-text="Screenshot showing Monitored Subscriptions selected in the Resource menu.":::
76-
77-
From **Monitored Subscriptions** in the Resource menu, select **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.
78-
79-
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.
80-
81-
Select the subscriptions you want to monitor through the Dynatrace resource and select **Add**.
82-
83-
:::image type="content" source="media/dynatrace-how-to-manage/dynatrace-add-subscription.png" alt-text="Screenshot showing subscriptions to add.":::
84-
85-
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**.
86-
87-
:::image type="content" source="media/dynatrace-how-to-manage/dynatrace-monitored-subscriptions-list.png" alt-text="Screenshot showing statuses of monitored subscriptions.":::
88-
89-
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.
90-
91-
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.
92-
9369
## Monitor virtual machines using Dynatrace OneAgent
9470

9571
You can install Dynatrace OneAgent on virtual machines as an extension. Select **Virtual Machines** under **Dynatrace environment config** in the Resource menu. In the working pane, you see a list of all virtual machines in the subscription.
@@ -98,11 +74,11 @@ For each virtual machine, the following info is displayed:
9874

9975
| Column | Description |
10076
|------------|------------|
101-
| **Name** | Virtual machine name. |
102-
| **Status** | Indicates whether the virtual machine is stopped or running. Dynatrace OneAgent can only be installed on virtual machines that are running. If the virtual machine is stopped, installing the Dynatrace OneAgent will be disabled. |
77+
| **Name** | The name of the virtual machine. |
78+
| **Status** | Indicates whether the virtual machine is stopped or running. Dynatrace OneAgent can only be installed on virtual machines that are running. If the virtual machine is stopped, installing the Dynatrace OneAgent is disabled. |
10379
| **OneAgent status** | Whether the Dynatrace OneAgent is running on the virtual machine. |
10480
| **OneAgent version** | The Dynatrace OneAgent version number. |
105-
| **Auto-update** | Whether auto-update has been enabled for the OneAgent. |
81+
| **Auto-update** | Whether autoupdate is enabled for the OneAgent. |
10682
| **Log monitoring** | Whether log monitoring option was selected when OneAgent was installed. |
10783
| **Monitoring mode** | Whether the Dynatrace OneAgent is monitoring hosts in [full-stack monitoring mode or infrastructure monitoring mode](https://www.dynatrace.com/support/help/how-to-use-dynatrace/hosts/basic-concepts/get-started-with-infrastructure-monitoring). |
10884

@@ -137,7 +113,7 @@ If you would like to reconfigure single sign-on, select **Single sign-on** in th
137113

138114
If single sign-on was already configured, you can disable it.
139115

140-
To establish single sign-on or change the application, select **Enable single sign-on through Microsoft Entra ID**. The portal retrieves Dynatrace application from Microsoft Entra ID. The app comes from the enterprise app name selected during the [pre-configuration steps](dynatrace-how-to-configure-prereqs.md).
116+
To establish single sign-on or change the application, select **Enable single sign-on through Microsoft Entra ID**. The portal retrieves Dynatrace application from Microsoft Entra ID. The app comes from the enterprise app name selected during the [preconfiguration steps](dynatrace-how-to-configure-prereqs.md).
141117

142118
## Delete Dynatrace resource
143119

0 commit comments

Comments
 (0)