Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LogsDB - elastic/security Serverless benchmark #698

Open
salvatore-campagna opened this issue Sep 23, 2024 · 1 comment
Open

LogsDB - elastic/security Serverless benchmark #698

salvatore-campagna opened this issue Sep 23, 2024 · 1 comment

Comments

@salvatore-campagna
Copy link
Contributor

salvatore-campagna commented Sep 23, 2024

Description

The elastic/security Serverless benchmark cannot be executed unless Kibana provides a method to install necessary resources—such as component templates, composable templates, and index templates—immediately when the esbench benchmark starts. Currently, the elastic/security track depends on Kibana to install these component templates, which are essential for proper data indexing.

At present, these resources are only installed after the user interacts with Kibana's UI, typically during the initial startup. This is a deliberate design choice by the security solutions team to delay resource installation until the first interaction, avoiding unnecessary installations. However, this optimization is not applicable in a Serverless environment, and future changes are expected to address this behavior.

For now, the recommended approach to set up the required resources is by using the following API call:

POST internal/detection_engine/prebuilt_rules/_bootstrap

Neither rally nor esbench currently support calling APIs outside of Elasticsearch, such as Kibana's APIs, which means we are unable to trigger the installation of these necessary resources at this time.

We need esbench to support calling such API at least when creating a Serverless project.

@elasticsearchmachine
Copy link

Pinging @elastic/es-storage-engine (Team:StorageEngine)

@martijnvg martijnvg transferred this issue from elastic/elasticsearch Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants