Thanks for answering promptly on this regard.
I'm working on the APM setup page, checking APM server availability.
Elastic, Kibana and APM are in three different Docker containers, I tested accesibility from each other and they can access through network (curl, ping, etc.).
Kibana connects and visualizes Elastic documents (dashboards, visualizations, etc)
Kibana and APM see each other from inside the containers (but Kibana's interface doesn't), still tries to reach a 'apm-*' index which I had created.
I ran testing commands: [ ./apm-server test config, ./apm-server test output ] and both are good (the check ouput is posted in this conversation thread).
Apparently, this steps only works having locally both (Localhost) and does not fit for distributed environment.
docker exec -it elastic-apm-server bash -c "./apm-server test config"
docker exec -it elastic-apm-server bash -c "./apm-server test output"
parse url... OK
parse host... OK
dns lookup... OK
dial up... OK
TLS... WARN secure connection disabled
talk to server... OK
But nothing happens. Even, the kibana container sees the apm-server one:
docker exec -it kibana-ui bash -c "curl -i http://elastic-apm-server:8200/"
HTTP/1.1 200 OK
host: "0.0.0.0:8200" # ":8200"
For APM Agent configuration in Kibana, enabled must be true.
Scheme and port can be left out and will be set to the default (
In case you specify an additional path, the scheme is required:
IPv6 addresses should always be defined as:
Optional protocol and basic auth credentials.
Thanks in advance.