## What is a custom service in Dynatrace?
- *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.* 
- *Another use case for custom services are microservices that are used by a larger application that aren't exposed via communication technologies.*

## How to create a custom service?
1. Open the file custom-service-java.yaml. 
2. Use customService1 as a template. Copy and paste it below, changing the skipDeployment to true.
3. Fill up all the remaining inputs with the details of the endpoint you're interested to monitor (className, methodName, etc...)
4. Commit and pull request to merge the branch to the master:
    `git add <changes>`
    `git commit -m "<app_name> configuration changes"`
	`git push -u origin <branch>`
5. Restart the application where the custom service has been created.
6. Check if the custom service appears in Dynatrace.

Notes: 
	- As this configuration needs a restart, it's better to create it in a non-Prod application.
	- The custom service will appear in Dynatrace iff there's traffic going through. 

## What if i have multiple classes?
1. Clone *template-1-1.json* to a new one called *template-2-1.json*.
2. Edit *template-2-1.json* adding a 2nd rule separated with a coma.
3. For the 2nd rule, change the name of the {{.values}} to {{.values2}} i.e. 
4. The template is ready to be used in the YAML file.

## What if i have multiple methods?
1. Same process as before, just call it template-1-2.json
2. In this way you can extend to a custom service with n classes and k methods: template-n-k.json