cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Difference in detecting services

Fisher
Frequent Guest

Hello team! Need your mind!

I have an issue with detecting services "from box". I have 2 clusters - IFT and NT. One service detecting have Service main technology = Apache tomcat (screens ift_0 and nt_0)
ift_0

 

ift_0.png


nt_0

 

nt_0.png

 

And on NT cluster Service main technology = Spring (screens ift_1, ift_1_1, nt_1). On NT cluster we can't capture similar Custom service.

ift_1

 

ift_1.png


ift_1_1

 

ift_1_1.png



nt_1

 

nt_1.png

 

In result, on NT cluster we see all requests as method calls Spring Controller, and on IFT cluster - we see as Web Request (screens ift_2, nt_2)

ift_2

 

ift_2.png

 



nt_2

 

nt_2.png

We can't use Custom service for similar controller's methods - it's don't capture this call (maybe, it's related to capturing "from box" have more higher priority level, and Custom service is duplicate endpoint, which was captured like controller's method).
I attached configuration 2 custom services - one from IFT cluster (it works), another from NT cluster (doesn't work) - ift_custom_service.json и nt_custom_service.json (in archive)

Why is this happening?

The problem in detection differences is widespread and, apparently, is not associated with any particular OpenShift cluster.

1 REPLY 1

techean
Dynatrace Champion
Dynatrace Champion

could you raise a support ticket, our expert will need to take a request for analysis. I suspect that some naming rules changes would be impacting the names. 

KG