Kibana version: 7.8.1
Elasticsearch version: 7.8.1
APM Server version: 7.8.1
APM Agent language and version: Java
Original install method (e.g. download page, yum, deb, from source, etc.) and version: yum
Fresh install or upgraded from other version? Fresh
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. No
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
We are having Weblogic (12.2.1) running in the production environment. We attached the stanalone apm jar to the PID. (Refer https://discuss.elastic.co/c/observability/apm/58)
We downgraded the APM version from 1.18 (standalone) to 1.17 (standalone).
When we accessed the Kibana APM services tab, the previously discovered services/traces etc dont' appear and only the service corresponding to 1.17 appears.
This is the exception while attaching the agent,
2020-09-15 13:00:54,748 [Attach Listener] INFO co.elastic.apm.agent.configuration.StartupInfo - Starting Elastic APM 1.17.0 as weblogic-PID-17 on Java 1.8.0_265 (Private Build) Linux 4.4.0-1113-aws
2020-09-15 13:00:54,748 [Attach Listener] WARN co.elastic.apm.agent.configuration.StartupInfo - To enable all features and to increase startup times, please configure application_packages
2020-09-15 13:00:54,831 [Attach Listener] INFO co.elastic.apm.agent.impl.ElasticApmTracer - Tracer switched to RUNNING state
2020-09-15 13:00:54,841 [elastic-apm-server-healthcheck] INFO co.elastic.apm.agent.report.ApmServerHealthChecker - Elastic APM server is available: { "build_date": "2020-06-14T17:10:16Z", "build_sha": "06c58bf4e5b675d04314bf44961ffd6b0e13f544", "version": "7.8.0"}
2020-09-15 13:00:54,918 [elastic-apm-remote-config-poller] ERROR co.elastic.apm.agent.configuration.ApmServerConfigurationSource - Remote configuration is not available. Check the connection between APM Server and Kibana.
Request your help in this.
-
On another note, is it possible to have a combination of java agents while monitoring applications - say Jboss monitored with 1.18 (standalone) and weblogic with 1.15 (standalone) agents.
-
When we use instrument as false , enable as false in elasticsearch.properties , the JVM related data is still coming to APM. Is that how the functionality is? Is that that only traces are not available.
Thanks again for all your help!
Regards,
Bhavani