Open vburckhardt opened 5 months ago
It'd be good to have this in place shortly after techxchange, I think this is one of the key value of the DA here compared to raw ES.
While we wait for this to be included in the ES DA I attempted the steps mentioned below from ICD Elasticsearch documentation that uses terraform to deploy Kibana on Code Engine.
I however run into this error and the Kibana instance on Code Engine never starts successfully.
2.706+00:00][INFO ][plugins-system.preboot] Stopping all plugins.
[2024-10-09T21:32:32.707+00:00][INFO ][plugins-system.preboot] All plugins stopped.
[2024-10-09T21:32:32.707+00:00][INFO ][plugins-system.standard] Stopping all plugins.
[2024-10-09T21:32:32.709+00:00][INFO ][plugins.monitoring.monitoring.kibana-monitoring] Monitoring stats collection is stopped
[2024-10-09T21:32:32.717+00:00][INFO ][plugins-system.standard] All plugins stopped.
[2024-10-09T21:32:32.720+00:00][INFO ][savedobjects-service] [.kibana] INIT -> FATAL. took: 115ms.
[2024-10-09T21:32:32.725+00:00][ERROR][savedobjects-service] [.kibana_security_solution] Action failed with 'There are no living connections'. Retrying attempt 1 in 2 seconds.
[2024-10-09T21:32:32.725+00:00][INFO ][savedobjects-service] [.kibana_security_solution] INIT -> INIT. took: 103ms.
[2024-10-09T21:32:32.727+00:00][ERROR][savedobjects-service] [.kibana_analytics] Action failed with 'There are no living connections'. Retrying attempt 1 in 2 seconds.
[2024-10-09T21:32:32.727+00:00][INFO ][savedobjects-service] [.kibana_analytics] INIT -> INIT. took: 109ms.
[2024-10-09T21:32:32.729+00:00][ERROR][savedobjects-service] [.kibana_ingest] Action failed with 'There are no living connections'. Retrying attempt 1 in 2 seconds.
[2024-10-09T21:32:32.729+00:00][INFO ][savedobjects-service] [.kibana_ingest] INIT -> INIT. took: 87ms.
[2024-10-09T21:32:32.733+00:00][ERROR][savedobjects-service] [.kibana_alerting_cases] Action failed with 'There are no living connections'. Retrying attempt 1 in 2 seconds.
[2024-10-09T21:32:32.733+00:00][INFO ][savedobjects-service] [.kibana_alerting_cases] INIT -> INIT. took: 107ms.
[2024-10-09T21:32:33.394+00:00][INFO ][plugins.screenshotting.chromium] Browser executable: /usr/share/kibana/node_modules/@kbn/screenshotting-plugin/chromium/headless_shell-linux_x64/headless_shell
FATAL Error: Unable to complete saved object migrations for the [.kibana_task_manager] index: The .kibana_task_manager alias is pointing to a newer version of Kibana: v8.12.2
(^ captured from the Code Engine deployed instance logs)
I believe you will run into this as well when adding Kibana capability to the DA.
@Ak-sky @vburckhardt can you suggest who is or will be working on this? Any insights to fix above issue in the interim will be very helpful.
deploy Kibana on Code Engine
@ajainghub, It is running fine as expected and I have not faced any issues, we can connect and have this issue resolved. Meanwhile I am working on ES-DA to integrate Kibana.
The deploy Kibana on Code Engine worked and deployed fine for Enterprise edition (8.12). The issue/errors I mentioned happen when I use Elasticsearch Platinum edition (8.12).
Description
Common use case to deploy kibana - I'd suggest to have automation to auto-deploy it as part of the DA (possibly as a stack). Some existing material: https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-kibana-code-engine-icd-elasticsearch