question

Edmund K. avatar image
Edmund K. asked ·

Service Merging

Hi,

When I want to merge several web request services together, it seems that the services have to originate from the same process group.

Is there a reason for this ?

services
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Hayden M. avatar image
Hayden M. answered ·

Hi Edmund,

James is correct - mergeable services must be apart of the same process group. This is to make sure that you are merging server side code that originates and lives in the same area on like hosts.

If this is necessary, though, this could be accomplished by setting up process group detection rules to merge the process groups together first. Here is a snippet from the Dynatrace documentation that explains in better detail:

"Dynatrace doesn't merge services that are hosted across multiple process groups, because each process group is considered to be a logical cluster. When Dynatrace detects the "same" service in separate process groups, it treats them as separate services (e.g., one process might be used in staging and the other in production). However, if you instruct Dynatrace to merge two separate process groups into a single group, this will also result in the services on those processes being merged as well."

https://www.dynatrace.com/support/help/infrastruct...

Hope this helps!
Hayden

Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

James K. avatar image
James K. answered ·

In Dynatrace services are server side code executed in a process group so by definition it makes sense to me that in order to merge services they would need to be part of the same process group. I don't have a ton of experience in this area yet so that is just my thought.

James

Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Space Topics

mobile monitoring dotnet synthetic monitoring reports iis chat kubernetes servicenow amazon web services mysql mainframe rest api errors cassandra dashboard oneagent sdk cmc application monitoring openkit smartscape request attributes monitoring developer community user tagging log monitoring services ufo syntheticadvisory activegate ip addresses auto-detection high five award oracle hyperion webserver uem usql iib test automation license web performance monitoring ios news migration management zones index ibm mq web services custom event alerts notifications sso host monitoring knowledge sharing reports browser monitors java hybris sap vmware maintenance window user action naming javascript appmon ai synthetic classic availability tipstricks automation extensions diagnostic tools session replay permissions davis assistant faq documentation problem detection http monitors server easytravel apdex aws-quickstart network docker tags and metadata cloud foundry google cloud platform synthetic monitoring process groups account usability dynatrace saas gui paas openshift key user actions administration user actions postgresql synthetic locations oneagent security Dynatrace Managed user management custom python technologies mongodb openstack user session monitoring continuous delivery citrix configuration alerting NGINX timestamp action naming linux nam installation masking error reporting database mission control jmeter recorder apache mobileapp RUM php threshold azure purepath davis scripting agent aix nodejs android