Kibana version: 7.6.2
Elasticsearch version: 7.6.2
APM Server version: 7.6.2
APM Agent language and version: elastic-apm-agent-1.15.0.jar
Browser version: Chrome
Original install method (e.g. download page, yum, deb, from source, etc.) and version: Download Page
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.
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
Hi It's my first time here, I ask apologize if my questions sounds like dummy.
I have an application based on JAVA that usage Wildfly 8 for webserver and JDK: 1.8.0_144.
I've implemented elastic with kibana, apm server in separated windows server (192.168.1.52)
In my tests i'm judge the elastic implementation it's works fine, but all time i'm trying implement the java agent on my application server it's not work, kibana not receive any data.
I'm following the agent configuration at below in standalone.conf in wildfly:
set "JAVA_OPTS=%JAVA_OPTS% -javaagent:D:\elastic\agent1150.jar" set "JAVA_OPTS=%JAVA_OPTS% -Delastic.apm.service_name=myapptest" set "JAVA_OPTS=%JAVA_OPTS% -Delastic.apm.server_urls=http://192.168.1.52:8200"
When I try to take a agent test in kibana (check the agent status): I received this message: No data has been received from agents yet
I've just tried to perform agent1150.jar file in cmd, and I receive this message at below:
C:\Windows\system32>java -javaagent:D:/elastic/agent1150.jar 2020-04-03 06:51:42.703 [main] INFO co.elastic.apm.agent.util.JmxUtils - Found JVM-specific OperatingSystemMXBean interface: com.sun.management.OperatingSystemMXBean 2020-04-03 06:51:43.000 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - Starting Elastic APM 1.15.0 as my-service on Java 1.8.0_144 (Oracle Corporation) Windows Server 2016 10.0 2020-04-03 06:51:43.000 [main] WARN co.elastic.apm.agent.configuration.StartupInfo - To enable all features and to increase startup times, please configure application_packages 2020-04-03 06:51:43.375 [main] INFO co.elastic.apm.agent.impl.ElasticApmTracer - Tracer switched to RUNNING state 2020-04-03 06:51:43.719 [elastic-apm-server-healthcheck] WARN co.elastic.apm.agent.report.ApmServerHealthChecker - Elastic APM server http://localhost:8200/ is not available (Connection refused: connect) Usage: java [-options] class [args...] (to execute a class) or java [-options] -jar jarfile [args...] (to execute a jar file) where options include: -d32 use a 32-bit data model if available -d64 use a 64-bit data model if available -client to select the "client" VM -server to select the "server" VM The default VM is client. -cp <class search path of directories and zip/jar files> -classpath <class search path of directories and zip/jar files> A ; separated list of directories, JAR archives, and ZIP archives to search for class files. -D<name>=<value> set a system property -verbose:[class|gc|jni] enable verbose output -version print product version and exit -version:<value> Warning: this feature is deprecated and will be removed in a future release. require the specified version to run -showversion print product version and continue -jre-restrict-search | -no-jre-restrict-search Warning: this feature is deprecated and will be removed in a future release. include/exclude user private JREs in the version search -? -help print this help message -X print help on non-standard options -ea[:<packagename>...|:<classname>] -enableassertions[:<packagename>...|:<classname>] enable assertions with specified granularity -da[:<packagename>...|:<classname>] -disableassertions[:<packagename>...|:<classname>] disable assertions with specified granularity -esa | -enablesystemassertions enable system assertions -dsa | -disablesystemassertions disable system assertions -agentlib:<libname>[=<options>] load native agent library <libname>, e.g. -agentlib:hprof see also, -agentlib:jdwp=help and -agentlib:hprof=help -agentpath:<pathname>[=<options>] load native agent library by full pathname -javaagent:<jarpath>[=<options>] load Java programming language agent, see java.lang.instrument -splash:<imagepath> show splash screen with specified image See http://www.oracle.com/technetwork/java/javase/documentation/index.html for more details. 2020-04-03 06:51:44.578 [elastic-apm-init-instrumentation-shutdown-hook] INFO co.elastic.apm.agent.impl.ElasticApmTracer - Tracer switched to STOPPED state 2020-04-03 06:51:44.578 [elastic-apm-init-instrumentation-shutdown-hook] INFO co.elastic.apm.agent.report.ApmServerReporter - dropped events because of full queue: 0 2020-04-03 06:51:44.593 [elastic-apm-init-instrumentation-shutdown-hook] INFO co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Reported events: 0 2020-04-03 06:51:44.593 [elastic-apm-init-instrumentation-shutdown-hook] INFO co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Dropped events: 0 2020-04-03 06:51:44.593 [elastic-apm-circuit-breaker] INFO co.elastic.apm.agent.impl.circuitbreaker.CircuitBreaker - Stopping the Circuit Breaker thread.
I Don't know if the jdk ver that i've in this server it's not compatible with this agent, ou it's some configuration that i'll need apply in standalone.conf