Welcome

• Hello and welcome to the Dynatrace Associate Certification Bootcamp!

• We’re happy you’re here. Please make sure that you’re ready for today’s session

• We recommend to use Chrome as your web browser for this training

• All content blocker extensions must be disabled for this training, e.g.:

• Alternatively, use an incognito/private browser window since extensions are disabled by default
(Note: You cannot use an Incognito window to trigger a recording of a synthetic clickpath monitor)

Confidential 1
 Rodrigo Pascoal

Dynatrace Associate
Partner Cloud Evangelist at
Dynatrace

Certification Bootcamp

Steve Weinert
Partner Cloud Evangelist at
Dynatrace
Participation expectations

• Eliminate distractions
• Cell phones
• E-mails
• Social media
• Notifications

• Exercise patience
• Express any challenges with one another
HELP! • Please mute your audio
• Place questions into chat or connection
raise your hand for assistance

Confidential 16
 Partner enablement journey

SALES SALES SALES SPECIALIST

TRAINING 2.5 hours 4 hours

SELF-PACED SELF-PACED

ASSOCIATE BOOTCAMP TECHNICAL SALES TRAINING

😊
ASSOCIATE 16 hours
TRAINING PROFESSIONAL TRAINING
INSTRUCTOR-LED HANDS-ON

TECHNICAL SALES TRAINING

TECHNICAL SALES 8 hours PROFESSIONAL TRAINING
TRAINING INSTRUCTOR-LED HANDS-ON

PROFESSIONAL BOOTCAMP
PROFESSIONAL 16 hours SERVICES TRAINING
TRAINING
INSTRUCTOR-LED HANDS-ON

Confidential 17
Frequently Asked Questions – Bootcamp

• Timing
• 16 hours in total
• Breaks every ~ 2 hours
• Lunch break

• Feedback
• Use Q&A for QUESTIONS
• Raise your hand for HELP (breakout rooms)
• Use green checkmark when exercise is complete

• Resources
• The session will NOT be recorded
• Slides will be shared at the end
• Environment will be terminated at the end of the bootcamp

Confidential 18
Frequently Asked Questions – Exam

• FREE Associate certification exam attempt voucher can be earned:

• Trainees that attend course in its entirety and
• Trainees that complete all quizzes and labs

• After receiving the voucher (sent typically the day after bootcamp ends):
• Exam must be taken within 14 days

TIP: Our data shows that the earlier the exam is taken, the higher the pass rate.

Confidential 19
FREE exam voucher reminder

• Exams must be scheduled and taken within 14 calendar days after the bootcamp

• Booking your spot early gives you the best chance to get your timeslot of choice

• Rescheduling is free when your exam is more than 24 hours away

• Rescheduling within 24 hours of your exam incurs a fee with the proctoring service

• Rescheduling beyond 14 calendar days after the bootcamp is not possible

Confidential 20
 The Dynatrace Software Intelligence Platform

All-in-one Platform

Multiple modules across

Biz/Dev/Sec/Ops

Unified AIOps for speed,

efficiency, simplicity

Built for webscale

Confidential 21
1. OneAgent 2. PurePath 3. Smartscape 4. Davis AI-Assistant 5. Grail

Continuous, automatic discovery & Distributed tracing and visibility Automatic, real-time topology AIOps with explainable answers Graph powered database for
observability across your full stack down to code-level. mapping with context. that drive self-healing & AI with limitless scale
automation.

Confidential 22
Demo

Confidential 23
Deployment models

Confidential 24
Deploying software and getting the best of both worlds

SaaS Managed

Dynatrace provides the service Customer provides the platform

Customer just use it. Dynatrace manages the service.

Confidential 25
Dynatrace SaaS

Confidential 26
Components - SaaS

Dynatrace OneAgents Web UI ActiveGate SaaS Cluster hosted in

(Optional) AWS, Azure, or Google
Cloud

Confidential 27
 Ports – SaaS
SaaS Cluster Hosted in Cloud Provider

Scale

443 https 443 https

Monitored applications

Dynatrace
OneAgents Web UI

Confidential 28
Ports – SaaS with ActiveGate
SaaS Cluster Hosted in Cloud Provider

Scale

443 https

443 https

ActiveGate
Monitored (Optional)
applications
9999 https
Dynatrace
OneAgents Web UI

Confidential 29
Updates

• The components are updated on the schedules below:

• SaaS cluster
• Every 2 weeks (automatic)

• OneAgent
• Every 4 weeks (optional, versions can be skipped)
• OneAgent versions are supported for 9 months
(12 months with Premium support)

Confidential 30
 Storage and retention - SaaS

Code-level Timeseries Real User Monitoring Other

(PurePaths and stacks traces) (Metrics) (User sessions and actions)

35 days 1 min. intervals for 35 days 35 days

Requests and 14 days User sessions Synthetic Monitoring
request attributes and mobile crashes (Browser and HTTP monitors)

10 days
Distributed trace and code 5 min. intervals for 35 days 35 days
insights 28 days User action data Log monitoring (without GRAIL)
and session replay

1 hr. intervals for 10 days

400 days Waterfall analysis

1 day intervals
5 years

31
https://www.dynatrace.com/support/help/shortlink/data-retention Confidential

Tooltips provide info on where data is coming from

Dynatrace Managed

Confidential 32
 Components - Managed

Dynatrace OneAgents Web UI

ActiveGate
(Optional)
Managed Cluster

Cluster Management Console Mission Control

(CMC) (possible via proxy)

Confidential 33
Ports - Managed

Managed Cluster

Mission Control
Scale
(possible via proxy)

443 https 443 https

ActiveGate
Monitored (Optional)
applications Web UI Cluster Management
9999 https Console (CMC)
Dynatrace
OneAgents

Confidential 34
 Storage and retention - Managed

Code-level Timeseries Real User Monitoring Other

(PurePaths and stacks traces) (Metrics) (User sessions and actions)

config max 365 days 1 min. intervals for 35 days config max 35 days
Requests and 14 days Sessions, user actions Synthetic Monitoring
request attributes and session replay (Browser and HTTP monitors)

config max 365 days config max 35 days

Distributed trace and code 5 min. intervals for config 5 to 90 days
User action data Log monitoring
insights 28 days and session replay

1 hr. intervals for config max 10 days

400 days Waterfall analysis

1 day intervals
5 years

35
https://www.dynatrace.com/support/help/shortlink/data-retention Confidential

Tooltips provide info on where data is coming from

Updates

• The components are updated on the schedules below:

• Managed Cluster
• Every 4 weeks (mandatory, can be delayed but versions cannot be skipped)
• Cluster versions are supported for 3 months (4 months with Premium support)

• OneAgent
• Every 4 weeks (optional, versions can be skipped)
• OneAgent versions are supported for 9 months
(12 months with Premium support)

• OneAgent updates are shipped together with the Cluster Upgrade

Confidential 36
Confidential 39
Mission Control

Confidential 40
Updating reliably and fully automatically

Dynatrace
Mission Control

Dynatrace cluster
t Dynatrace Update
v+1 be
a
a rt
He Dynatrace Mission Control Team

Confidential 41
Remote management

Dynatrace
Dynatrace Managed Cluster Mission Control
Request for access

Dynatrace node 1 t v ia Dy
e I na h
o ck s eU t ra t t p Request for access
s p a c ce s
e b h t t n atr VP
W y N
o rD on
Dynatrace node 2 l yf ly
on

Dynatrace Mission Control Team

Access cluster management

Dynatrace node n Access each environment
Access an internal maintenance UI

Confidential 42
What Data is sent to Mission Control?

System settings
Usage &
Event tracking
billing

Health Software
statistics updates
Confidential 43
Monitoring environments

Confidential 44
Monitoring environments – Synonyms

Monitoring environment
=
Environment
=
Tenant
Confidential 45
Monitoring environments – Definition

• A Dynatrace monitoring environment is where all the analysis takes place

• A OneAgent sends captured monitoring data to a single monitoring environment for analysis

• A monitoring environment is essentially a dedicated tenant on a multi-tenant platform

Environment A Environment B

Confidential 46
Monitoring environments – Example segmentation based on deployment stages

Production

Staging

Development

Confidential 47
Monitoring environments – Example segmentation based on geography/data residency

AMERICAS

EMEA

GLOBAL R&D

Confidential 48
ActiveGates

Confidential 49
What is an ActiveGate?

• Acts as a relay between the OneAgent and Dynatrace

ü Reduce firewall changes

ActiveGate
ü Compress traffic between datacenters and Dynatrace
ü Run extensions to monitor components that can’t be
instrumented directly with a OneAgent

• No extra configuration: install where OneAgents can

connect to it and the rest is handled automatically!

• ActiveGates can be configured to communicate through

a proxy server

Confidential 50
Hosts with direct access to Dynatrace

Database

ActiveGates are technically

optional because OneAgents can
connect directly to Dynatrace

Confidential 51
Hosts without direct access to Dynatrace

Database

In corporate environments,
firewalls would need to be
configured to allow outgoing
traffic from each OneAgent

Confidential 52
Hosts without direct access to Dynatrace

Database

A better approach is to use an

ActiveGate, which makes it possible to
use a single firewall rule for all
OneAgents in that network segment
that are connected to the ActiveGate

ActiveGate

Confidential 53
Hosts within isolated network segments

Database

ActiveGate ActiveGate

DMZ Network X

Confidential 54
 ActiveGates ports

https
443
Dynatrace
Directly OneAgents

SaaS or Managed

https

https
9999

443
Via ActiveGate
Dynatrace
OneAgents ActiveGate

SaaS or Managed

Confidential 55
Types of ActiveGates

Environment ActiveGate Cluster ActiveGate

Dynatrace SaaS Dynatrace SaaS

Dynatrace Managed Dynatrace Managed
Confidential 56
Environment ActiveGates

Definition
An Environment ActiveGate is bound to a specific environment,
and thus only handles traffic from OneAgent instances that
belong to the same monitoring environment.

Connectivity
An Environment ActiveGate can handle traffic from OneAgents,
not from other ActiveGates.

Installation
Environment ActiveGate The Environment ActiveGate installer is downloaded from the
monitoring environment itself.

Dynatrace SaaS Deploy Dynatrace > Install ActiveGate

Dynatrace Managed
Confidential 57
 Cluster ActiveGates

Definition
A Cluster ActiveGate is bound to a Dynatrace Managed cluster,
and thus can handle traffic from OneAgent instances that belong
to any environment that exists on the cluster.

Connectivity
A Cluster ActiveGate can handle traffic from any OneAgents
as well as from any Environment ActiveGate that exist on
the same cluster.

Installation
Cluster ActiveGate
The Cluster ActiveGate installer is downloaded from the Cluster
Management Console (CMC) interface.

CMC > “… “ button > Install Cluster ActiveGate

Dynatrace SaaS
Dynatrace Managed
Confidential 58
 ActiveGates on SaaS

Green
Environment Green EAG
OneAgents

Environment Blue EAG Blue

OneAgents

Environment Red EAG Red

OneAgents

Monitored
Dynatrace servers
SaaS
Customer

Synonyms: Monitoring environment = Environment = Tenant EAG = Environment ActiveGate Confidential 59

ActiveGates on Managed – Customer hosted

Environment Green EAG Green

OneAgents

Environment Blue EAG Blue

OneAgent
s

Environment Red EAG Red

OneAgents

Green
OneAgents
Cluster CAG Blue Red
OneAgents OneAgents

Dynatrace Managed Monitored

servers

Customer

Synonyms: Monitoring environment = Environment = Tenant 60

EAG = Environment ActiveGate | CAG = Cluster ActiveGate
Confidential
ActiveGates on Managed – Partner hosted

Environment Green EAG Green

OneAgents

Environment Blue EAG Blue

OneAgent
s

Environment Red EAG Red

OneAgents

Green
OneAgents
Cluster CAG Blue Red
OneAgents OneAgents

Dynatrace Managed Monitored

servers

Partner Customer

Synonyms: Monitoring environment = Environment = Tenant 61

EAG = Environment ActiveGate | CAG = Cluster ActiveGate
Confidential
ActiveGates on Managed – Alternative connectivity scheme: EAG via CAG

Environment Green EAG Green

OneAgents

Environment Blue EAG Blue

OneAgent
s

Environment Red EAG Red

OneAgents

Green
OneAgents
Cluster CAG Blue Red
OneAgents OneAgents

Dynatrace Managed Monitored

servers

Partner Customer

Synonyms: Monitoring environment = Environment = Tenant 62

EAG = Environment ActiveGate | CAG = Cluster ActiveGate
Confidential
ActiveGate connectivity

• Level 1: Environment ActiveGates

• Level 2: Cluster ActiveGates
• Level 3: Embedded ActiveGates—ActiveGates embedded within cluster nodes
Notes

• ActiveGates can only send data to higher hierarchy levels. ActiveGates cannot send data to the
same or lower level of the hierarchy.
• Environment ActiveGates, by default, connect directly to the Dynatrace Cluster. This eliminates
an intermediate step of connecting to a Cluster ActiveGate. Connecting through the Cluster
ActiveGate needs to be arranged.

• Connectivity can also depend on network zones if such are configured. Network zone
configuration means that ActiveGates and OneAgents will prefer to communicate with
ActiveGates from the same zone, before connecting to ActiveGates outside of the active zone.
Confidential 63
Additional ActiveGate capabilities

• Integrations with other platforms

• AWS, Azure, vCenter, Kubernetes

ActiveGate
• Run synthetic tests from within own (private) network

• Store memory dumps

• Run extensions

• Receive Real User Monitoring beacons

• Mainframe monitoring

Confidential 64
Recap - Do I need an ActiveGate?

Install an ActiveGate if you need to:

• Limit the number of firewall changes

• Introduce load balancing for monitoring

data within a large deployment

• Lower network bandwidth through

compression and bundling of traffic
• ~30% reduction in network traffic

• Monitor virtualization

• Capture agentless RUM, Mobile RUM

and Synthetic traffic

• Deploy ActiveGate Extensions

Confidential 65
 Recap - Do I need an ActiveGate?

Capability Cluster ActiveGate Environment ActiveGate

Agentless/Mobile RUM Yes
External Synthetic Monitors Yes
AWS integration Yes Yes
Azure integration Yes Yes
Cloud Foundry integration Yes Yes
VMware integration Yes Yes
Kubernetes/OpenShift integration Yes Yes
Private Synthetic location Yes Yes
Memory dump storage Yes Yes
Mainframe CICS/IMS Yes
ActiveGate Extensions Yes

https://www.dynatrace.com/support/help/technology-support/cloud-platforms/amazon-web-services/supporting-services/
Confidential 66
 A – Environment ActiveGate
B – Cluster ActiveGate
Refresher C – Managed Cluster
D – Mission Control

Datacenter #1 Datacenter #2 Datacenter #3

OneAgents OneAgents
OneAgents

Environment Environment
ActiveGate ActiveGate
3 Cluster 3
2
ActiveGate

1
CMC
Dynatrace 4
Scale
Managed Cluster Mission Control

Confidential 67
Web UI
 A – 443 https
B – 80 http
Refresher C – 80 https
D – 9999 https

Datacenter #1 Datacenter #2 Datacenter #3

OneAgents OneAgents
OneAgents

9999 https 9999 https

9999 https
1 1 1

Environment Environment
ActiveGate 9999 https 9999 https ActiveGate
2 2 3
3 2 Cluster
ActiveGate

443 https 4
3 443 https
1
CMC
443 https Dynatrace 4
3 Scale
Managed Cluster Mission Control

Confidential 68
Web UI
ENJOY YOUR BREAK

Confidential 69
Quiz 1

Quiz participation is
required for eligibility
of a FREE exam
voucher

https://dt-url.net/yiytbp
Confidential 71
Bootcamp environment

Confidential 72
Dynatrace lab environment

• Navigate to the URL below to get your lab environment credentials:

https://dt-url.net/lookup

Confidential 73
UI walkthrough

• How do I access Dynatrace?

• How do I adjust timeframes?

• How is the menu structured?

• Where do I go to manage Dynatrace?

Confidential 74
UI walkthrough

Confidential 75
Demo application

Confidential 80
 easyTravel

Application consists of:

• Java processes
• C++
• A Java Derby Database
• Apache Web Server

User interface
• Legacy web interface
• Single-page app interface
(Angular)

Download your own copy on the Dynatrace Community site

Confidential 81
 Environment
H TTPS 443
443
H TTP S
Env #1
SSH 22 Trainee #1
jump
Env #2

Env #1 Env #2 Env #3 Env #n

Env #3 ….
H TTP S
443

….

Scale

Managed Cluster

Env #n

Mission Control
Confidential 82
Lab activity
 Tip: To change the color scheme
and other settings of your web shell
Lab activity: Check SSH and easyTravel
CTRL + ALT + SHIFT

1. Connect to your VM instance

CTRL + CMD + SHIFT

2. Verify if easyTravel is running by

typing service easytravel status

(should show as active)

3. Test your personal easyTravel links

in the launchpad dashboard

Confidential 87
OneAgent

Confidential 88
OneAgent

• Currently supported OS:

• Linux, Solaris, AIX, Windows, and z/OS operating systems, Kubernetes platforms, etc

• Communication from OneAgent to Dynatrace is outbound only

• OneAgent can communicate directly to Dynatrace (port 443) or it can communicate

via Dynatrace ActiveGate (port 9999)

• Different ways of installing:

• Manually
• Automatically
• Group policy for Windows
• Using automation tools like Ansible, Chef, Puppet, etc.

• OneAgent auto-update is enabled by default but can be disabled globally, per host group, or per host.

https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/capabilities/how-one-agent-works/
Confidential 89
 OneAgent Installation Options

Distributed traces

Code-level & microservices

CPU & memory profiler

Metrics & extensions

Log files & events

Processes

Infrastructure only
Containers & orchestration

Full Stack
Network & devices

Servers & virtualization

https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/capabilities/supported-monitoring-types/
Confidential 90
Lab activity
Lab activity: OneAgent Installation

1. Login to your environment (tenant)

2. From the menu, select

Manage -> Deploy Dynatrace

3. Click Start installation and select Linux

4. Click Create token to generate PaaS Token

5. Do install step 1, step 2, step 3

DON’T forget to run the installer with
root rights: sudo /bin/sh/Dynatrace...

6. Verify the deployment by clicking

Manage -> Deployment status
in your environment

Confidential 92
OneAgent Installation

Confidential 93
OneAgent Installation

Confidential 94
Hosts

Confidential 95
Hosts in the Smartscape

• Hosts represented with the operating system

logos are physical or virtual machines where
OneAgent is deployed

• Generic host symbols are used to signify

monitoring candidates – i.e., unknown hosts
that are detected because they receive
TCP/IP requests from monitored hosts

• Inactive connections or hosts are visualized

with dashed lines

• Cloud services and custom devices are also

represented at host level

Confidential 96
Confidential 97
Lab activity
Lab activity – Adapt host settings

1. In your environment, go to Manage ->

Settings -> Monitoring -> Host Naming

2. Create a new rule

• Name: EC2 Public Hostname
• Host name format:
AWS - {Ec2Instance:PublicHostName/[^.]++}
• Conditions: Public EC2 host name exists

3. Verify rule by clicking Preview

4. Save the rule

Confidential 99
Adapt Host Settings

Confidential 10
0
ENJOY YOUR BREAK

Confidential 10
1
Processes

Confidential 10
4
Process Group Instance

• A Process Group Instance is a single process that belongs to a designated Process Group

• A process can be identified as running on one unique host, container etc.

• Technology aligned metrics include:

• Process CPU
• JVM metrics
• AppServer metrics
• System performance
• Web server
requests

Confidential 10
5
Processes in the Smartscape

• Processes are host-centric, associated with a

single machine in your environment.

• Each node in the Smartscape corresponds to a

process group instance

• Each connection represents a TCP/IP request

• Dashed lines show inactive connections

between processes during the last 2 hours

• A connection ages out and is no longer shown

in Smartscape if has been inactive for more
than 72 hours

Confidential 10
6
Process Groups
PG
• A logical group of process
instances that perform some type
of organizational function PGI PGI

• The underlying processes must run

the same software technology
and perform the same function
Host Host

Data
Center

= tangible = logical
Confidential 10
7
Process Groups

• Processes are grouped

automatically (at process restart)
with built-in detection rules that
can be adapted

• Metrics are available at process

group level and for each process
group instance separately

Confidential 10
8
Process Group Availability

• Critical processes can be monitored for availability at process group level

• An availability problem is triggered when:
• any process instance in the process
group becomes unavailable
• a user-defined threshold for the
minimum number of running processes
within a process group isn’t met

Confidential 10
9
Process Group Detection

• By default, OneAgent only tracks process group types that are considered important (others are aggregated)

• Valuable process group types that Dynatrace reports on by default:

• Application processes (for example, Java, .NET, Node.js, PHP and Go)
• Web server processes (for example, Apache and IIS)
• Databases processes (for example, MS SQL, Oracle, MySQL and Cassandra)
• Processes that have an open TCP listening port
• Processes for which CPU, memory usage or network traffic exceeds 5% within 3 samples taken within 5 minutes

• It also provides an option to explicitly monitor other processes that don’t fall in these categories

Confidential 11
0
Lab activity
Lab activity: Process group detection

1. In your environment, go to Manage ->

Settings -> Processes and containers ->
Declarative Process Grouping -> Add monitored
technology
2. Add a monitored technology name
• Technology name: Linux top

3. Add process group

• Process group display name: top
• Process identifier: toplinux

4. Add detection rule

• Process property: Executable path
• Condition: $eq(/usr/bin/top)

5. In your web shell/SSH terminal launch top

Confidential 11
2
Hands On: Process Detection

Confidential 11
3
Hands On: Process Detection

Confidential 11
4
Hands On: Process Detection

Confidential 11
5
Process Group Deep Monitoring

• Beside detecting and monitoring the process health, the OneAgent can additionally provide deep monitoring
for supported technologies (think full-stack)

• The same way there are rules to process group detection there are also built-in rules to include or exclude
specific processes from deep analysis

• Custom rules are also available to suit the needs for specific process monitoring
• You may have a few unimportant, or short-lived processes that you do not want to monitor at a code level
• You may not be able to run deep monitoring on applications that belong to your customers and are
outside of your control
• You want to have strict control over which processes are monitored

Confidential 11
6
Lab activity
Lab activity: Process group deep monitoring

1. In your environment, go to Manage -> Settings ->

Processes and containers -> Custom process
monitoring rules -> Add custom rule

2. Create a new rule

• Mode: Do not monitor
• Condition target: Command line args
• Condition operator: contains
• Condition value: CommandlineLauncher

3. In your web shell SSH terminal restart easyTravel

sudo service easytravel restart

4. Verify the CommandlineLauncher process group is

no longer deeply monitored

Confidential 11
8
Hands On: Process Group Monitoring (by creating an environment rule)

Confidential 11
9
Hands On: Process Group Monitoring (at Deployment Status)

Confidential 12
0
Hands On: Process Group Monitoring (at Host level)

Confidential 12
1
Hands On: Process Group Monitoring (at global PG level)

Confidential 12
2
Hands On: Process Group Monitoring Status

Confidential 12
3
Services

Confidential 12
4
Services

• A set of code or classes that performs some type of business logic

• Services are where transactions occur

• Example: Your travel website has functions/requests (add to cart, sign in, search etc.)
• The Customer front end service contains these functions or requests within the service

• Services often call other services to get the task or request completed.
• Search requests usually call a database service

• Services usually fall under common types:

• Web requests
• Web services
• Database Calls
• Message Queues
• Custom Services

Confidential 12
5
Services in the Smartscape

• Services are logical groupings that run on a

Process Group or Process Group Instance
• Services are request-centric and therefore
typically span across multiple machines in a
data center.
• Special type of services:
• Opaque services are services that are detected
on the calling side by Dynatrace for which code-
level visibility isn't available i.e. with
unsupported/unrecognized technology
• External dependencies are services that
represent outgoing calls to systems that aren't
monitored in the environment. There are two
types of external dependencies, calls to
public networks (public IP/domains) and calls
to unmonitored hosts (internal IP)

Confidential 12
6
Confidential 12
7
Service flow and service backtrace

• Service flow provides an overview of all services and • Service backtrace will provide the upstream view
queues that a selected service makes requests to and
the time spent within those services • When would I use service backtrace?
• Understand what services call the selected service
• When would I use the service flow?
• Analyze the performance of a service from the
• Understand the call chain sequence of a service
perspective of the calling clients
• View all the response time contributors for a service
• Ex: Finding where traffic overloading a database is
• View affected tiers during active or resolved
coming from
problems

Confidential 12
8
Custom Services

• If your application services aren’t built on standard technologies, they may not be
recognized out-of-the box

• You can monitor these technologies, but you’ll need to define them as custom services with
specific service entry points

• Dynatrace allows you to define any method, class, or interface as the entry point of a service
to be monitored

• Java, .NET, PHP, Go, and Node.js

services are currently supported

• Each custom service may contain

multiple entry points

Confidential 12
9
Custom Services

• For Java and PHP it’s possible

to have changes to custom
services applied automatically
by enabling Real-time
updates to Java (or) PHP
services

• For other technologies,

processes must be restarted
before changes are applied

Confidential 13
0
Lab activity
Lab activity: Custom service detection

1. In your environment, go to Manage -> Settings ->

Server-side service monitoring -> Deep monitoring

2. Under Real-time updates to Java and PHP services

turn on Enable real-time updates to Java services

3. Go to Settings -> Service Detection -> Custom service

detection and then click Define Java services
• Name your custom service: CheckDestination
• Select the process group: …backend.jar easytravel-*-x*
• Search for loaded classes: …webservice.JourneyService
• Select the discovered class
• Choose: Use the selected class
• Select public Boolean checkDestination (java.lang.String)
• Save changes

• Extra credit: Find CheckDestination in a service flow

Confidential 13
2
Hands On: Custom Services

Confidential 13
3
Hands On: Custom Services

Confidential 13
4