Kibana version: 6.6.0
Elasticsearch version: 6.6.0
APM Server version: 6.6.0
APM Agent language and version:
Browser version: N/A
Original install method:
Java using the agent jar
Fresh install or upgraded from other version?
Fresh install
Is there anything special in your setup?
No special setup as far as I am aware, just followed the guide on setting up the APM agent. I am using the APM server in the cloud option, and have the obtained the server URL and secret token from there.
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
When setting up the APM Java agent in the docker container that I have running, the agent thows an error saying:
ERROR co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Failed to handle event of type METRICS with this error: Connection refused (Connection refused)
I have included the connection information in the elasticapm.properties file, as can be seen below:
############################################
# Core #
############################################
Type: Boolean
Default value: true
active=true
Type: Boolean
Default value: true
instrument=true
# The name of your service
# This setting can not be changed at runtime. Changes require a restart of the application.
Type: String
Default value: Main
service_name=Main
# A version string for the currently deployed version of the service. If you don’t version your deployments, the recommended value for this field is the commit identifier of the deployed revision, e.g. the output of git rev-parse HEAD.
#
# This setting can not be changed at runtime. Changes require a restart of the application.
# Type: String
# Default value:
#
service_version= 1.0
# The name of the environment this service is deployed in, e.g. "production" or "staging".
Type: String
#Default value:
environment=test
# By default, the agent will sample every transaction (e.g. request to your service). To reduce overhead and storage requirements, you can set the sample rate to a value between 0.0 and 1.0. We still record overall time and the result for unsampled transactions, but no context information, tags, or spans.
Type: Double
#Default value: 1.0
transaction_sample_rate=1.0
# Limits the amount of spans that are recorded per transaction.
# This is helpful in cases where a transaction creates a very high amount of spans (e.g. thousands of SQL queries).
# Setting an upper limit will prevent overloading the agent and the APM server with too much work for such edge cases.
# This setting can be changed at runtime
Type: Integer
#Default value: 500
transaction_max_spans=500
Type: Level
#Default value: INFO
log_level=DEBUG
#This setting can not be changed at runtime. Changes require a restart of the application.
Type: comma separated list
Default value: https://7aea994c47fc41749d1faa5a9e48b604.apm.us-east-1.aws.cloud.es.io:443
server_urls= https://7aea994c47fc41749d1faa5a9e48b604.apm.us-east-1.aws.cloud.es.io:443
# This setting can not be changed at runtime. Changes require a restart of the application.
# Type: String
# Default value:
secret_token=XXXXXXXXXXXXXXXX
Summary
I am not sure what is missing that is causing the connection to be refused, but imagine that perhaps there is a step that I am missing. Any assistance would be greatly appreciated.
