Service communication with application

[ArtuD]

Having a communication problem between an application and the services it communicates with, what could be responsible for this? The frontend captures user actions normally, but inside the frontend it shows us that there is no service being called, what could be happening?

[AntonPineiro]

Hi,

Have you installed OneAgent in fullstack mode in application servers?

Best regards

[ArtuD]

Yes, was installed on fullstack mode

[AntonPineiro]

Hi,

And you can see services discovered in relation to processes in fullstack?

Best regards

[Peter_Youssef]

Hi @ArtuD 

PFA comment for resolution:

• FW and network Blocking header issue: https://docs.dynatrace.com/docs/observe/digital-experience/web-applications/initial-setup/firewall-c...
• The related Oneagent technologies related features are enabled properly and the related services are restarted whenever possible.
• Distributed tracing features are enabled accurately as per the monitored technologies.

• Another factor to consider is enabling the Real User Monitoring on the related process groups and Process group deep monitoring activation will be an added value as well.
• Check if the application services falls under the below categories ingest-from/extend-dynatrace/extend-tracing/oneagent-sdk 

Validate the app frameworks are enabled accurately

Hoping it helps.

BR,

Peter

[ArtuD]

Hello Peter! Just to give you context, this problem is happening in just one of the applications, the others communicate normally.

[ArtuD]

The service that this application is supposed to communicate with is being monitored, it is a technology that dynatrace supports. There is just no interaction between the two.

[Peter_Youssef]

Hi @ArtuD 

Ensure there is no issue with Adaptive traffic management as well:

• https://docs.dynatrace.com/managed/analyze-explore-automate/distributed-traces/adaptive-traffic-mana...

BR,

Peter

[Peter_Youssef]

Hello @ArtuD 

Another factor to consider validation, is it supported technology by Dynatrace Or Not:

• https://docs.dynatrace.com/docs/ingest-from/technology-support

KR,

Peter

[RohitBisht]

One of the possible reasons is stripping of the headers Dynatrace uses to stitch frontend and backend. You can define a request attribute to capture these headers in services and see if that is the reason.

Maybe your firewall or application is blocking/stripping these headers. Pease check if these are allowed.
x-dynatrace
x-dynatrace-application

https://docs.dynatrace.com/docs/shortlink/rum-firewall#headers

[PacoPorro]

I agree with @RohitBisht , looks like a problem stitching RUM with user actions.
https://community.dynatrace.com/t5/Open-Q-A/X-dynaTrace-header-missing/m-p/182169