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

HTTP 403 requests shwing under a different service ("localhost")

Delary
Observer

 

Hey everyone!

I’m running into something strange in a customer environment and hoping someone here can help me understand it.

We have a Java SpringBoot application running on several VMs, and other several NGINX servers acting as reverse proxies to route traffic to this app. Dynatrace OneAgent is installed and successfully monitoring the environment.

Here’s the situation:

There’s a controller in the Java SpringBoot application called StartApplicationController, and it has a @PostMapping for the path /s/ac/iniciar. In Dynatrace, this controller appears as a service and shows only HTTP 200 (successful) requests.

However, we’re also seeing a separate Java SpringBoot service named "localhost" (within the same process group) that shows requests to the exact same path, /s/ac/iniciar, but only those with HTTP 403 (forbidden) responses.

This seems odd to me. I would expect both the 200 and 403 requests to appear under the same service (StartApplicationController).

Any ideas why this is happening?

Thanks in advance,
Delary
0 REPLIES 0

Featured Posts