Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Mid Server Monitoring

cardanid
Tera Contributor

Hello community, has anyone attempted to monitor the Mid Server with a APM tool like Dynatrace or Datadog?

1 ACCEPTED SOLUTION

It should look something like below in the wrapper-override.conf file:

wrapper.java.additional.<n>=-javaagent:/path/to/dd-java-agent.jar

Here, <n> is a unique number that doesn't clash with other wrapper.java.additional settings.

You'd need to make sure the path to dd-java-agent.jar is correct and accessible by the MID Server process.

Also, restart the server when the change in completed in wrapper-override.conf.

View solution in original post

11 REPLIES 11

trueframe
Kilo Contributor

Mid-server monitoring is the process of continuously observing and analyzing the performance, health, and activity of intermediate-level servers within your IT infrastructure. These servers sit between a client device and a backend server or database, often acting as an intermediary and handling various tasks such as data processing, authentication, and routing requests.

cardanid
Tera Contributor

Issue resolved thanks to a new relic post. if you want to add APM via Datadog or New Relic or Dynatrace, you add to the wrapper-override file. 

 

# Adding Datadog Java Agent
wrapper.java.additional.3=-javaagent:D:\\ServiceNow\\DataDogJava\\dd-java-agent-0.107.1.jar
-Ddd.service=
-Ddd.env=
- Ddd.tags=
-Ddd.profiling.enabled=
-Ddd.new_gc_metrics=
-Ddd.trace.sample.rate=