Trouble configuring agent server

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 :slight_smile:

Kibana version: 7.1.1

Elasticsearch version: 7.1.1

APM Server version: 1.x current

APM Agent language and version: English

Browser version: Chrome

Original install method (e.g. download page, yum, deb, from source, etc.) and version: java -javaagent:/path/to/elastic-apm-agent-.jar
-Delastic.apm.service_name=my-application
-Delastic.apm.server_url=http://localhost:8200
-Delastic.apm.secret_token=
-Delastic.apm.application_packages=org.example
-jar my-application.jar

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.
Unable to execute the "java -javaagent" command and can't find the file.

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):

Problem with : "Start the application with the javaagent flag"

You are using the wrong jar. You need to use the elastic-apm-agent-1.9.0.jar.
See related documentation.

java -javaagent:"/etc/apm-agent/elastic-apm-agent-1.9.0.jar" -Delastic.apm.service_name=apm-agent1 -Delastic.apm.server_url=http://10.0.0.0:8200 -Delastic.apm.secret_token= -Delastic.apm.application_packages=https://site.com.sg -jar elastic-apm-agent-1.9.0.jar

Is this correct? But it still showing "Error: Invalid or corrupt jarfile elastic-apm-agent-1.9.0.jar"

That part -jar elastic-apm-agent-1.9.0.jar
Should be your app jar not the agent jar

Ohh, I just noticed your command is trying to install our java agent on the java agent attaching process...
You really mixed up things.
Please take a close look at the setup documentation.
You either install an agent using the javaagent option, or using the attach, not both

Hi thanks for explaining. May I know this is to monitor and capture the Java application data?

What if the server only has Nginx, do we still install this Java agent on this server? Sorry I am new on this and unsure of the process.

Hi could you share with me where can I get a clearer explanation on this? I am quite confused with the elastic documentation. Thanks

I am doing this is to get the APM to work on my Ubuntu and Linux server.

I currently don't know of any other resource we have other than the setup documentation.
Normally, this is what users read when starting. Please be more specific in what is not clear enough.

Previously I was thinking to use the "Automatic setup" method to setup the agent, so to follow the original configuration and setting, that is why I choose this version of .jar file. https://www.elastic.co/guide/en/apm/agent/java/current/setup-attach-cli.html ........ Am I correct to say that?

Yes, the Java agent is only for capturing Java application data. It cannot monitor NginX. There are other components to collect logs and metrics data for NginX.

Sorry, may i know what are those?

All, how can I check the required index is in the hosting server (Kibana) ?

How can I import the required fields in order for me to build / load the kibana visualization.

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.