You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've just start playing with the apm server in our cluster, in older releases of kibana/elastic/apm-server (6.5.X) we could monitorize nodejs apps, but after the upgrade to 6.8.0 we can't.
Today, my infrastructure looks like:
Kibana version: 6.8.0
Elasticsearch version: 6.8.0
Server OS version: Centos 7.3
Browser version: Chrome 70
Installed and updated with yum
In the monitored app we are using:
Nodejs v10.15-3
elastic-apm-node 2.11.5 (we've updated after start seen the error "No transactions were found.")
To reproduce the issue we need to go to the APM tab, and select a nodejs service. After that we need to select an specific transaction and an empty transactions window appear :
This call does a "SELECT 1" in the DB.
The same setup using bootstrping or tomcat apps, is working.
Logs:
{"type":"response","@timestamp":"2019-05-31T13:39:26Z","tags":[],"pid":3807,"method":"get","statusCode":404,"req":{"url":"/api/apm/services/suma-sso-rest/transaction_groups/request/GET%20/health/charts?start=2019-05-30T13%3A39%3A25.838Z&end=2019-05-31T13%3A39%3A25.839Z","method":"get","headers":{"x-real-ip":"xxxx","host":"xxxx","connection":"upgrade","kbn-version":"6.8.0","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36","content-type":"application/json","accept":"*/*","referer":"http://xxxx/kibana/app/apm","accept-encoding":"gzip, deflate","accept-language":"es-ES,es;q=0.9,en;q=0.8","true-client-ip":"5.5.5.5"},"remoteAddress":"10.153.0.47","userAgent":"10.153.0.47","referer":"http://xxxx/kibana/app/apm"},"res":{"statusCode":404,"responseTime":82,"contentLength":9},"message":"GET /api/apm/services/suma-sso-rest/transaction_groups/request/GET%20/health/charts?start=2019-05-30T13%3A39%3A25.838Z&end=2019-05-31T13%3A39%3A25.839Z 404 82ms - 9.0B"}
{"type":"response","@timestamp":"2019-05-31T13:39:26Z","tags":[],"pid":3807,"method":"get","statusCode":404,"req":{"url":"/api/apm/services/suma-sso-rest/transaction_groups/request/GET%20/health/distribution?start=2019-05-30T13%3A39%3A25.838Z&end=2019-05-31T13%3A39%3A25.839Z","method":"get","headers":{"x-real-ip":"xxxx","host":"xxxx","connection":"upgrade","kbn-version":"6.8.0","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36","content-type":"application/json","accept":"*/*","referer":"http://xxxx/kibana/app/apm","accept-encoding":"gzip, deflate","accept-language":"es-ES,es;q=0.9,en;q=0.8","true-client-ip":"5.5.5.5"},"remoteAddress":"10.153.0.47","userAgent":"10.153.0.47","referer":"http://xxxx/kibana/app/apm"},"res":{"statusCode":404,"responseTime":82,"contentLength":9},"message":"GET /api/apm/services/suma-sso-rest/transaction_groups/request/GET%20/health/distribution?start=2019-05-30T13%3A39%3A25.838Z&end=2019-05-31T13%3A39%3A25.839Z 404 82ms - 9.0B"}
The text was updated successfully, but these errors were encountered:
Hi all,
We've just start playing with the apm server in our cluster, in older releases of kibana/elastic/apm-server (6.5.X) we could monitorize nodejs apps, but after the upgrade to 6.8.0 we can't.
Today, my infrastructure looks like:
Kibana version: 6.8.0
Elasticsearch version: 6.8.0
Server OS version: Centos 7.3
Browser version: Chrome 70
Installed and updated with yum
In the monitored app we are using:
Nodejs v10.15-3
elastic-apm-node 2.11.5 (we've updated after start seen the error "No transactions were found.")
To reproduce the issue we need to go to the APM tab, and select a nodejs service. After that we need to select an specific transaction and an empty transactions window appear :
This call does a "SELECT 1" in the DB.
The same setup using bootstrping or tomcat apps, is working.
Logs:
The text was updated successfully, but these errors were encountered: