Custom service Entry points question

[raffaele_talari]

Hi there,

is there any way to "restrict" the Entry points settings to specific services/hosts?

I only see this setting available under the global settings, as shown in the screenshot below:

Thanks in advance for your help.

Ciao,

Raff

[michael_kopp · Accepted solution]

The Custom Services define a service, so restricting it to a service is not possible. We are currently adding the ability to restrict it to a set of process groups or a host group though. Would that fullfill this requirement?

[raffaele_talari]

Hi Michael,

yeah I think so. That would be great, thanks!

Ciao,
Raff

[raffaele_talari]

@Michael K. two quick questions about this:

- Is there going to be "Filtering by tag" functionality?

- When we would expect to get this feature (roughly)?

Thanks a lot,

Raff

[bemdumaguing]

Hello, just wondering if there's an update on this..

I have defined 2 Custom Services (they have the same entry point but pointed to different hosts/processes).

Custom Service Name: CustomService1

Entry Point: custom.service.entry.point

Hosts: Host1, Host2

Custom Service Name: CustomService2

Entry Point: custom.service.entry.point

Hosts: Host3, Host4

When checking Host1 services, I see CustomService1 as expected. But when checking the Host3 services, I am expecting to see CustomService2, but instead, I see CustomService1.

Is this really how this works or am I missing a configuration?

Is there a way to restrict custom services to a process/host only?

Thank you.

[michael_kopp]

We are planning a feature that would allow to specify a Custom Service for a set of Process Groups. We are also planning a feature that would work similar to the tagging feature to cover dynamic environments. ETA most likely this year.

[Yosi_Neuman]

Hi Michel

Any update or ETA for Custom Service for a set of Process Groups

Yos

[rick_boyd]

If you edit your custom service, there is a "Optionally restrict custom service rules by process groups" section you can use

[satish_a_prasad]

@Michael K., Is there a performance benefit (ie in speed of instrumentation) to scope this to specific process groups? I assume that the default behavior is "check if this class is loaded in the process" in ALL process groups.. which may be expensive..?

I'm comparing it to Appmon where specific sensor rules could be applied to specific agent groups.. and i recollect there was advisory that is a best practice in improving instrumentation speed..

[RaviSivaPrasad_]

Very valid point. Dynatrace must relook into this API design. With current implementation, with deep monitoring enabled, it created a huge outage across our platform. All components bound to dynatrace, started scanning for newly defined custom service, caused huge CPU demand to underlying shared platform. This Custom Service should be restricted to specific process groups, to avoid this issue