If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text
TIP 1: select at least one tag that further categorizes your topic. For example server
for APM Server related questions, java
for questions regarding the Elastic APM Java agent, or ui
for questions about the APM App within Kibana.
TIP 2: Check out the troubleshooting guide first. Not only will it help you to resolve common problems faster but it also explains in more detail which information we need before we can properly help you.
Kibana version: v8.2.0 (Elastic Cloud)
Elasticsearch version:
APM Server version: v8.2.0 (Elastic Cloud)
APM Agent language and version: Java 1.31.0
Browser version:
Original install method (e.g. download page, yum, deb, from source, etc.) and version: Elastic Cloud
Fresh install or upgraded from other versions?: Fresh
Is there anything special in your setup? No, services communicate through Public APIs
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
The inter service communication between services in a microservice based application is not accurate for the services communicating with each other through public APIs. Elastic APM considers the public endpoints as a different service and does not actually connect with the service that is instrumented with Elastic APM. The services are hosted on the same cluster of Azure Spring Cloud and all services use Java Spring with the same elastic agent version.
The actual flow of transaction -
Elastic APM Service Map-
As you can see, there are no links to produce service but there are new services for the public endpoints called
Steps to reproduce:
- Deploy a simple microservice based application that communicates with each other through publically exposed REST APIs.
- Instrument one service with APM and perform a transaction that hits all services in the application.
- Instrument the rest of the application for all services.
- View the service map in the kibana dashboard and the service links are not accurate
Errors in browser console (if relevant): N/A
Provide logs and/or server output (if relevant):