Loadbalancer shows up as unmonitored endpoint even though OneAgent is deployed on application servers behind it

[rsmsdk]

Hi

-----------

We have a network issue that I believe is header related, but I need advise on how to adress it to our managed service provider.

-----------

An example of infrastructure running services related to this issue:

1. Frontendhost01-02 with OneAgent installed

2. Servicebushots01-02 with OneAgent installed

3. Backendhost01-02 with OneAgent installed

-----------

Expected:

End-to-end purepath (trace) of service transactions between the three host.

-----------

Scenario:

Purepath (trace) from Frontendhost01-02 through Servicebushost01-02 but then hit a loadbalancer URL endpoint infront of Backendhost01-02 that should be transparent, and is identified as unmonitored by Dynatrace. No trace data from Backendhost01-02 is present, untill we see a response on Servicebushost01-02 from the unmonitored loadbalancer endpoint.

-----------

The loadbalancer in front of Backendhost01-02 seem to act as a roadblock for trace correlation, and is causing end-to-end traces to be fragmented, as the trace on Backendhost01 is present but as an individual trace with no relation to the parent trace initiated from Frontendhost01.

-----------

I tried to look up documentation on loadbalancer configuration, but can only find stuff related to RUM?

-----------

Any advise on how I should adress this to our MSP is greatly appriciated.

-----------

Best regards

[Mizső]

Hi @rsmsdk,

Have you already tried this setting?

I hope it helps.

Best regards,

Mizső

[rsmsdk]

Hi @Mizső

The gRPC headers are disabled. Do you know where I can read up on those, and what they do?

Thank you for taking your time.

Best regards

[Mizső]

Hi @rsmsdk

Could you please check it?

gRPC

Best regards,

Mizső