question

James L. avatar image
James L. asked ·

How can I stop my service from being split into Web request, RMI, and Background types?

We have over 250 JVMs that are pretty monolithic. Right now, every single JVM is being split into three service types, but that is not helpful nor accurate for our architecture. How can we prevent 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.

Gil G. avatar image
Gil G. answered ·

@Michael K. I think the most "bothering" issue we see on customer sites is the creation of the background activity service, which, in async environments create a difficulty to isolate flows. It would be great if at least this could be controlled.

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.

Hayden M. avatar image
Hayden M. answered ·

Hi James,

Based on your last comment, something that may help would be setting up custom service naming rules to help you better identify these services from the process group view. This can be done by going to Settings --> Server side service monitoring --> Service naming rules. You could set one up for each service type you're seeing (RMI, web request, background, etc.) and add something to help you better identify which is which in quick manner.

HTH,
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.

Michael K. avatar image
Michael K. answered ·

May I ask, you said you have these 3 services for each JVM. Should those 250 JVMs all be standalone. Or is it that multiple of these JVMs do the same thing and should form a process group? the reason I ask is that process groups split services. a process group is thought to contain many instances (processes/JVMs) of the same deployment. Thus maybe in your case we first need to start adjusting process grouping, the services would then automatically fold as a consequence.

A single service would then have many instances (aka JVMs). It would be treated as such.

Does this make sense?

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 L. avatar image
James L. answered ·

I'm learning to work around it. But for us folks still supporting legacy systems, it would be nice to have this as a configurable option. Or at least have the Service type listed by the individual services in the Process group view - that would prevent me from opening the wrong service each time I try one of the three.

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 L. avatar image
James L. answered ·

The entry point is not an issue. The issue is that we don't derive any value of Dynatrace arbitrarily demarcating parts of our app based on request type. This is all handled internally with highly controlled thread pools.

1 comment 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.

AFAIK you don't have any control over this. It's just grouping of services based on the request type. If services are not correctly detected, you can merge services or create new custom ones as @Jordan C. suggests. Does this grouping into categories cause any issues for you?

0 Likes 0 · ·
Jordan C. avatar image
Jordan C. answered ·

Hi James,

Do you have any details on why this isn't accurate for your architecture? One option available to you would be to define your own custom services. This allows you to define any method, class, or interface as the entry point to a service.

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 session replay diagnostic tools 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