APM Server has still not connected to Elasticsearch

Elastic Observability APM
1

Hi Guys,
i installed APM server and config it to connect to my elastic,
when i click " APM Server status" button i get the following message: "APM Server has still not connected to Elasticsearch"

although in apm -server when i ran apm-server -e i got the following output:
2019-05-28T17:43:04.612+0300 INFO [http_client] beater/client.go:49 HTTP Server ready
2019-05-28T17:43:04.612+0300 INFO [onboarding] beater/onboarding.go:36 Publishing onboarding document
2019-05-28T17:43:05.613+0300 INFO pipeline/output.go:95 Connecting to backoff(elasticsearch(http://esh-prod-elasticsearch-01.eqx.solaredge.com:9200))
2019-05-28T17:43:05.613+0300 INFO pipeline/output.go:95 Connecting to backoff(elasticsearch(http://esh-prod-elasticsearch-03.eqx.solaredge.com:9200))
2019-05-28T17:43:05.613+0300 INFO pipeline/output.go:95 Connecting to backoff(elasticsearch(http://esh-prod-elasticsearch-05.eqx.solaredge.com:9200))
2019-05-28T17:43:05.613+0300 INFO pipeline/output.go:95 Connecting to backoff(elasticsearch(http://esh-prod-elasticsearch-04.eqx.solaredge.com:9200))
2019-05-28T17:43:05.613+0300 INFO pipeline/output.go:95 Connecting to backoff(elasticsearch(http://esh-prod-elasticsearch-02.eqx.solaredge.com:9200))
2019-05-28T17:43:05.616+0300 INFO elasticsearch/client.go:734 Attempting to connect to Elasticsearch version 6.6.0
2019-05-28T17:43:05.616+0300 INFO elasticsearch/client.go:734 Attempting to connect to Elasticsearch version 6.6.0
2019-05-28T17:43:05.616+0300 INFO elasticsearch/client.go:734 Attempting to connect to Elasticsearch version 6.6.0
2019-05-28T17:43:05.620+0300 INFO template/load.go:129 Template already exists and will not be overwritten.
2019-05-28T17:43:05.620+0300 INFO [index-management] idxmgmt/supporter.go:196 Loaded index template.
2019-05-28T17:43:05.620+0300 INFO elasticsearch/client.go:734 Attempting to connect to Elasticsearch version 6.6.0
2019-05-28T17:43:05.621+0300 INFO pipeline/output.go:105 Connection to backoff(elasticsearch(http://x.x.x.x:9200)) established
2019-05-28T17:43:05.624+0300 INFO template/load.go:129 Template already exists and will not be overwritten.
2019-05-28T17:43:05.624+0300 INFO [index-management] idxmgmt/supporter.go:196 Loaded index template.
2019-05-28T17:43:05.624+0300 INFO pipeline/output.go:105 Connection to backoff(elasticsearch(http://x.x.x.x:9200)) established
2019-05-28T17:43:05.626+0300 INFO elasticsearch/client.go:734 Attempting to connect to Elasticsearch version 6.6.0
2019-05-28T17:43:05.628+0300 INFO template/load.go:129 Template already exists and will not be overwritten.
2019-05-28T17:43:05.628+0300 INFO [index-management] idxmgmt/supporter.go:196 Loaded index template.
2019-05-28T17:43:05.628+0300 INFO pipeline/output.go:105 Connection to backoff(elasticsearch(http://x.x.x.x:9200)) established
2019-05-28T17:43:05.667+0300 INFO template/load.go:129 Template already exists and will not be overwritten.
2019-05-28T17:43:05.667+0300 INFO [index-management] idxmgmt/supporter.go:196 Loaded index template.
2019-05-28T17:43:05.667+0300 INFO pipeline/output.go:105 Connection to backoff(elasticsearch(http://x.x.x.x:9200)) established
2019-05-28T17:43:05.672+0300 INFO template/load.go:129 Template already exists and will not be overwritten.
2019-05-28T17:43:05.672+0300 INFO [index-management] idxmgmt/supporter.go:196 Loaded index template.
2019-05-28T17:43:05.672+0300 INFO pipeline/output.go:105 Connection to backoff(elasticsearch(http:/x.x.x.x:9200)) established

Kibana version:
"6.6.0"
Elasticsearch version:
"6.6.0"
APM Server version:
7.1

Do you have any idea why check button show failure?
Thanks

2

This is happening because apm-server 7.1.0 requires elasticsearch and kibana 7.0.0 or greater. In your case, we'd suggest upgrading Elastisearch and Kibana to 7.1 if possible. Otherwise, downgrade apm-server to 6.8.0.

3

Thanks Gil,
Already figured it out!

4

Glad to hear it!

5

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