Kibana version:
7.16.2
Elasticsearch version:
7.16.2
APM Server version:
1.34.1
APM Agent language and version:
Java 1.34.1
Browser version:
Latest Chrome
Original install method (e.g. download page, yum, deb, from source, etc.) and version:
Docker
Fresh install or upgraded from other version?
Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.
We run our back and frontend behind a YARP proxy that will forward automatically to keycloak and add JWT's to backend calls
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
Before this setup (so no gateway/oauth) our APM/APM java agent setup was able to give use detailed tracing information. When changing to this setup I still find the transactions in APM but not the linked trace information.
instead of
Steps to reproduce:
1.Both installations use the same APM configurations
2.When moving back to old situation the trace logging is back
3.
Errors in browser console (if relevant):
No errors
Provide logs and/or server output (if relevant):