Skip to content

Commit 2d13470

Browse files
authored
Merge pull request MicrosoftDocs#2930 from dlepow/dynatrace
Adding Dynatrace article submitted through public repo
2 parents c852d6b + 96d35fb commit 2d13470

File tree

7 files changed

+60
-0
lines changed

7 files changed

+60
-0
lines changed
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
title: Monitor an Azure Container Service DC/OS cluster with Dynatrace | Microsoft Docs
3+
description: Monitor an Azure Container Service DC/OS cluster with Dynatrace. Deploy the Dynatrace OneAgent by using the DC/OS dashboard.
4+
services: container-service
5+
documentationcenter: ''
6+
author: MartinGoodwell
7+
manager: ''
8+
editor: ''
9+
tags: acs, azure-container-service
10+
keywords: Containers, DC/OS, Azure
11+
12+
ms.assetid:
13+
ms.service: container-service
14+
ms.devlang: na
15+
ms.topic: article
16+
ms.tgt_pltfrm: na
17+
ms.workload: na
18+
ms.date: 12/13/2016
19+
ms.author: rogardle
20+
21+
---
22+
# Monitor an Azure Container Service cluster with Dynatrace SaaS/Managed
23+
In this article, we show you how to deploy the [Dynatrace](https://www.dynatrace.com/) OneAgent to monitor all the agent nodes in your Azure Container Service cluster. You need an account with Dynatrace SaaS/Managed for this configuration.
24+
25+
## Dynatrace SaaS/Managed
26+
Dynatrace is a cloud-native monitoring solution for highly dynamic container and cluster environments. It allows you to better optimize your container deployments and memory allocations by using real-time usage data. It is capable of automatically pinpointing application and infrastructure issues by providing automated baselining, problem correlation, and root-cause detection.
27+
28+
The following figure shows the Dynatrace UI:
29+
30+
![Dynatrace UI](./media/container-service-monitoring-dynatrace/dynatrace.png)
31+
32+
## Prerequisites
33+
[Deploy](./container-service-deployment.md) and [connect](./container-service-connect.md) to a cluster configured by Azure Container Service. Explore the [Marathon UI](./container-service-mesos-marathon-ui.md). Go to [https://www.dynatrace.com/trial/](https://www.dynatrace.com/trial/) to set up a Dynatrace SaaS account.
34+
35+
## Configure a Dynatrace deployment with Marathon
36+
These steps show you how to configure and deploy Dynatrace applications to your cluster with Marathon.
37+
38+
1. Access your DC/OS UI via [http://localhost:80/](http://localhost:80/). Once in the DC/OS UI, navigate to the **Universe** tab and then search for **Dynatrace**.
39+
40+
![Dynatrace in DC/OS Universe](./media/container-service-monitoring-dynatrace/dynatrace-universe.png)
41+
42+
2. To complete the configuration, you need a Dynatrace SaaS account or a free trial account. Once you log into the Dynatrace dashboard, select **Deploy Dynatrace**.
43+
44+
![Dynatrace Set up PaaS integration](./media/container-service-monitoring-dynatrace/setup-paas.png)
45+
46+
3. On the page, select **Set up PaaS integration**.
47+
48+
![Dynatrace API token](./media/container-service-monitoring-dynatrace/api-token.png)
49+
50+
4. Enter your API token into the Dynatrace OneAgent configuration within the DC/OS Universe.
51+
52+
![Dynatrace OneAgent configuration in the DC/OS Universe](./media/container-service-monitoring-dynatrace/dynatrace-config.png)
53+
54+
5. Set the instances to the number of nodes you intend to run. Setting a higher number also works, but DC/OS will keep trying to find new instances until that number is actually reached. If you prefer, you can also set this to a value like 1000000. In this case, whenever a new node is added to the cluster, Dynatrace automatically deploys an agent to that new node, at the price of DC/OS constantly trying to deploy further instances.
55+
56+
![Dynatrace configuration in the DC/OS Universe-instances](./media/container-service-monitoring-dynatrace/dynatrace-config2.png)
57+
58+
## Next steps
59+
60+
Once you've installed the package, navigate back to the Dynatrace dashboard. You can explore the different usage metrics for the containers within your cluster.
131 KB
Loading
57.1 KB
Loading
14.4 KB
Loading
208 KB
Loading
57.5 KB
Loading
189 KB
Loading

0 commit comments

Comments
 (0)