[BUG] No all the indices created on local Elasticsearch

[jgrobles]

Bug Description

After performing a local installation and connecting the analytics component to an on-premises Elasticsearch instance, only the achilles-risk-acceptances index is created.

Even after executing the corresponding tests, this index remains empty, occupying only 249 bytes.

In order for the analytics functionality to work completely, the remaining indices must be created manually by clicking the "Create" option under the Settings section.

Please refer to the attached screenshots for reference.

Module Affected

• [ x ] Analytics (Elasticsearch integration)

Expected behavior:

During the integration process, all required indices should be created automatically in order to start storing the executed test results and enable analytics and decision-making based on those results.
A clear and concise description of what you expected to happen.

Environment

• Elasticsearch Server OS: Ubuntu 22.04
• Elasticsearch Server: 8.19.14
• Agent OS: Windows 11

This is what you have when you do the fresh installation.

Then you have to manually click "Create" at the Setting Panel.

This is the final result when you got the proper indices.

[ubercylon8]

Hi Jonathan. Can you confirm this was under the Docker installation procedure?
I'm asking this because I recently modified local development procedure and I'm quite sure all indices are produced (there is even a script for this only - creating indices). So it will make sense to me if this is a non-local dev installation type issue.

[jgrobles]

This setup corresponds to a local installation intended to use an existing ELK infrastructure.

In the final architecture, a dedicated Achilles server sends logs to a dedicated Elasticsearch server, which also collects logs from other platforms within the local network.

[ubercylon8]

I'm not able to reproduce it in the current version and using local dev installation script and procedure. I do identify another issue though kind of adjacent but not exactly what you are stating. Let me take a deeper look and will get back to you.