Open dkarlovi opened 5 months ago
Pinging @elastic/apm-ui (Team:APM)
Alternatively, downgrading to APM version 7.17.21 seems to work as a workaround.
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)
@dkarlovi I noticed the same error in my ECK but the error disappeared when I've redeployed my kibana with the required xpack for apm.
@peowpeowbangbang you mean if you don't install the plugin via the UI but via deployment config?
Kibana version:
8.13.0
Elasticsearch version:
8.13.0
Server OS version:
Docker
Browser version:
Google Chrome 124.0.6367.118 (Official Build) (64-bit)
Browser OS version:
Fedora Linux 40
Original install method (e.g. download page, yum, from source, etc.):
Docker image
Describe the bug:
When onboarding to APM, there seems to be a catch 22 of sorts:
Steps to reproduce:
When I use "Check APM Server status" on
/kibana/app/home#/tutorial/apm
I get:
but, from the APM server logs, I keep getting
From my understanding reading a bunch of ES docs, forums and error messages, Kibana will install these templates (as evidenced in the errors), but Kibana doesn't seem to think the APM server is running, even though it is and it's accessible from Kibana's container:
Expected behavior:
Kibana sees the APM server and installs the templates (or installs the templates even if it cannot see the APM server?)
Alternatively, Kibana explains what it tried to do when checking and provide a hint how the APM server could be made available (for example, if it's a configuration issue, what APM server endpoint did it try and how to change that).
Screenshots (if relevant):
Errors in browser console (if relevant):
N/A
Provide logs and/or server output (if relevant):
There's no relevant error logs.