Update: I enabled a full web service rule to detect a service as a web request service by setting a condition on <NameService.svc>. It seems to be tracking correctly, so I’m considering making this the default rule without conditions, as it applies to multiple scenarios. Has anyone experienced a service being split into two entities: a web request service and a web service?
######
Hi All,
I'm seeking guidance on best practices for creating a service detection rule. We have a service in our environment that is being detected as two separate entities, which is causing discrepancies in our alerting. Currently, it's recognized as <NameEntryPoint.API> and <NameService.svc>, but it should be detected as <NameEntryPoint.API>\<NameService.svc>.
I've reviewed the documentation (Service detection rules - Dynatrace Docs), but I'm looking for specific best practices or recommendations on how to address this issue effectively. Any insights or advice would be greatly appreciated.
Sincerely,
Lance
