Introduction

Test environment

• Virtual machine 1:
  • Name: gl-145-pr
  • vCPU: 1
  • RAM: 1 GB
  • IP: 192.168.56.2
• Virtual machine 2:
  • Name: gl-463-rc
  • vCPU: 1
  • RAM: 1 GB
  • IP: 192.168.56.3

REMINDER: This lab is dedicated to Dynatrace configuration but since it is an advanced lab, you will need DevOps concepts and knowledge that are not specific to Dynatrace but will be used in your configurations. You will need the following skills, for which you can follow the free training:

• Docker: View training
• Vagrant: View training
• Traefik: View training
• Prometheus: View training
• Grafana: View training
• DevOps: View training

Of course, we will provide as much information as possible to help you advance even without these prerequisites.

git clone https://github.com/RousselTM/dynatrace-formation
cd dynatrace-formation/tp
vagrant up

Pre-configuration

Dynatrace Agent

What you will learn in this section :

• Install a dynatrace agent: oneagent
• Understand available parameters
• Reconfigure an agent

1. Installation

   You must install the oneagent on the machine 'rousseltm-prod-1' by setting the hostgroup as 'PROD_TP'.

   INFORMATION: To prepare your transition to IaC, we recommend downloading the sources via CLI. In addition to the IaC advantage, the URL will automatically provide the version corresponding to the Dynatrace server updates. This avoids version mismatch between the console and the agents.

2. Verifications

   You must access the dynatrace console and verify that your machine shows up properly. Which application shows the machines that report? You must also verify that the hostgroup shows up properly. Which application can also allow you to see all the elements on which there is a oneagent?

3. Les PATH

   During an installation, it may be necessary to modify the default folders to adapt to disk formatting. You must provide the configurations to set during agent installation to customize:
   • Installation folder
   • Logs folder
   • ...

4. Reconfiguration

   As indicated in the training, we might need to modify parameters of the oneagent for various reasons: setup error, missing parameter, migration to a new cluster...

   CRITICAL: The easy way would be to reinstall the agent but resulting in the creation of a new ID and therefore the loss of history. You must therefore reconfigure it instead. Oneagent reconfiguration

   You must therefore modify the agent's configuration to add or update:
   • hostgroup: PROD_TP1
   • TAGS: ENV=PROD, PROJECT=P1, APP=A1
   • Owner: T1
   Remember to check again if your modification is properly taken into account in the console.

Discovery

1. Mapping

   You must find how to get the mapping of your infrastructure: Datacenter, machines, processes...

Configuration

What you will learn in this section :

• Optimize your infra/costs
• Disable monitoring of processes, containers, ...
• choice of operators

1. Host

   You must configure Dynatrace so that it renames the machines following this template:
   • All machines with Hostgroup: '$HOSTGROUP - $DETECTEDNAME'
   • All machines without Hostgroup: 'ERROR - $DETECTEDNAME'

2. Process group

   Dynatrace will automatically group processes it judges identical together (if it does not identify a Hostgroup). You will have different applications on Docker that it will group while in reality they are different. You must create the configuration to force dynatrace to separate them based on the 'ROUSSELTM_APP' environment variable:

3. Services

4. Tags

   You must add a configuration that will create on all services of type 'Web request service' the tag 'ROUSSELTM_APP' with the value being the server name content.

   CRITICAL: Ideally, in a company, you must ensure that each entity has the minimum number of tags to identify: direction, department, team, project ...

   We also want the 'Host' and the 'Process group' hosting them to inherit these tags.

5. Zones

   As you have noticed, all entities are put together. For this demo environment it is not a problem but in a company it will be necessary to create management zones to organize this.

   REMINDER: In addition to allowing the classification of entities in dynatrace, it will also allow you to manage security.

   You must therefore create a management zone that will contain all services, process groups, machines having the tag 'ROUSSELTM_APP=APP1'

   REMINDER: In a company, you will have to add other rules in the management zone to take into account other elements APPLICATION, DATABASES, ...

6. Process

   By default, Dynatrace will collect information on everything it discovers. In a company, you will have processes, containers ... that you do not want to monitor. You must configure Dynatrace so that it does not monitor all containers ending in '-build'.

   REMINDER: You already have default configurations in Settings -> Processes and containers -> Built-in container monitoring rules

7. Serverless

   Your company uses serverless? You must enable the configuration so that Dynatrace can detect your containers.

Owners

What you will learn in this section :

• Management and assignment of teams
• using dt.owner and owner

1. Creation

   You must create the team 'Project 1' with the following characteristics:
   • Team name: Project 1
   • Description: your description
   • Team ID: project1
   • Functions: Development and Operations

2. Assignment

   You must assign this team to all VMs/containers of the team in question.