APM Setup Success but is not showing information into Kibana

[Ramon_Sanchez_Villan (Ramon Sanchez Villanueva)]

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

Kibana version:
7.3.1
Elasticsearch version:
7.3.1
APM Server version:
7.3.1
APM Agent language and version:
java and 1.10
Browser version:
Chrome
Original install method (e.g. download page, yum, deb, from source, etc.) and version:
downloaded from page
Fresh install or upgraded from other version?
Fresh installation
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.
I'm using Kibana, APM-Server, APM-Agent and ElasticSearch
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
I was putted APM agent into two tomcat instance, and APM-server is receiving information from agents without issue. But problem is for one tomcat instance is not showing information into Kibana Web UI for APM and for this tomcat instance, but for the other one is show fine. Both tomcats are into same server.

Checking into Discover, informatio is there like you can look below screen shot:

Steps to reproduce:
1.Intall Agent into Tomcat instance
2.Bring up all services for Elastic (Elastic, Kibana and APM-SERVER)
3.Check into Kibana Web UI

Errors in browser console (if relevant):
No errors is seeming
Provide logs and/or server output (if relevant):
This below log is coming from APM-Server:
2019-10-02T04:35:19.318-0500 INFO [request] beater/common_handler.go:185 handled request {"request_id": "9daf27a3-4a08-4393-aad4-a4ab498c1dd0", "method": "POST", "URL": "/config/v1/agents", "content_length": 404, "remote_address": "127.0.0.1", "user-agent": "elasticapm-java/1.10.0", "response_code": 304}
2019-10-02T04:35:24.977-0500 INFO [request] beater/common_handler.go:185 handled request {"request_id": "f84e65c0-7b8d-4a66-b438-b8702ed58e66", "method": "POST", "URL": "/config/v1/agents", "content_length": 397, "remote_address": "127.0.0.1", "user-agent": "elasticapm-java/1.10.0", "response_code": 304}
2019-10-02T04:35:27.039-0500 INFO [request] beater/common_handler.go:185 handled request {"request_id": "72a6e838-b93d-4244-8d63-5667f8e0bc42", "method": "POST", "URL": "/intake/v2/events", "content_length": -1, "remote_address": "127.0.0.1", "user-agent": "elasticapm-java/1.10.0", "response_code": 202}
2019-10-02T04:35:31.773-0500 INFO [request] beater/common_handler.go:185 handled request {"request_id": "05e9094c-943b-4c92-860b-aad6cb1004ab", "method": "POST", "URL": "/intake/v2/events", "content_length": -1, "remote_address": "127.0.0.1", "user-agent": "elasticapm-java/1.10.0", "response_code": 202}
2019-10-02T04:35:49.331-0500 INFO [request] beater/common_handler.go:185 handled request {"request_id": "868b94d7-ffdd-4327-868d-19db51f831af", "method": "POST", "URL": "/config/v1/agents", "content_length": 404, "remote_address": "127.0.0.1", "user-agent": "elasticapm-java/1.10.0", "response_code": 304}
2019-10-02T04:35:54.990-0500 INFO [request] beater/common_handler.go:185 handled request {"request_id": "7499dc6d-f4e9-4645-a43d-56d5953cc684", "method": "POST", "URL": "/config/v1/agents", "content_length": 397, "remote_address": "127.0.0.1", "user-agent": "elasticapm-java/1.10.0", "response_code": 304}
2019-10-02T04:35:57.041-0500 INFO [request] beater/common_handler.go:185 handled request {"request_id": "ae13ed6b-0783-41f2-a75e-1742255d6402", "method": "POST", "URL": "/intake/v2/events", "content_length": -1, "remote_address": "127.0.0.1", "user-agent": "elasticapm-java/1.10.0", "response_code": 202}
2019-10-02T04:36:01.776-0500 INFO [request] beater/common_handler.go:185 handled request {"request_id": "4c7bd612-98b5-4c33-88d4-cc94dca9153a", "method": "POST", "URL": "/intake/v2/events", "content_length": -1, "remote_address": "127.0.0.1", "user-agent": "elasticapm-java/1.10.0", "response_code": 202}

[Eyal_Koren]

Hi Ramon, welcome to the community!

Please describe what exactly it is that you are missing- if you filter based on the tomcat listening port using the query bar (eg url.port : 8080) - can you see transactions only for one of them?

Or is the problem you can view data (like metrics) from each instance separately?
If so, please see this issue that will add the ability to configure separate node names and filter on them, specifically for these cases where two instances of the same service are deployed on the same host.

[Ramon_Sanchez_Villan (Ramon Sanchez Villanueva)]

Dear Eyal,

I was deployed APM agent into Tomcat as web site explained. I deployed same procedure on other tomcat and it's working fine. When I'm looking into Kibana using Discover, and I'm trying to look information for service I have problem I found it without problem and I'm using this query "service.name: iris-testserver-webaxn":

When I'm trying to use APM option into Kibana, Service is showing:

But when I make click over Service and I'm trying to look information collecting by APM Server and Agent is not showing nothing:

But for other Java Tomcat is showing information without issue.

How I can release why is not showing information?

Regards

[Eyal_Koren]

It seems that this tomcat is only sending metrics data, not traces.
Which of the listed supported technologies are used by this app?