elastic/kibana

[Security Solution] [Bug] Getting `An error occurred during service entity store resource initialization` while enabling Entity Store in SPACE with long name

Open

#240057 opened on Oct 22, 2025

View on GitHub
 (5 comments) (0 reactions) (0 assignees)TypeScript (19,065 stars) (8,021 forks)batch import
Entity Store (Next)Team: SecuritySolutionTeam:Core Analysisbuggood first issueimpact:hightriage_neededv9.2.0

Description

Describe the bug Getting An error occurred during service entity store resource initialization while enabling Entity Store in SPACE with long name

Kibana/Elasticsearch Stack version

VERSION: 9.2.0
BUILD: 91875
COMMIT: 68626ce831ffb8e4138bb24ba8762a15a569a41c

Pre Conditions

  1. Kibana v9.2.0 must be available.
  2. SPACE with a LongName should be available.

Steps to reproduce

  1. Login to pre requisite SPACE.
  2. Navigate to Stack Management -> Entity Store.
  3. Enable Entity Store.
  4. Observe that there will be error as An error occurred during service entity store resource initialization

Expected Results User should be able to enable Entity Store in SPACE with long name

Observation

Contributor guide

Tech stack
typescriptelasticsearch
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Kibana development setupNode.js and TypeScriptElasticsearch basicsKnowledge of Spaces feature
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Investigate the Entity Store initialization code to find where the space name is used and might cause issues with long names. Look for any string length constraints or formatting that could break. Check if the error originates from the Kibana server or Elasticsearch. Relevant files include those under x pack/plugins/security solution or spaces plugin. Review comments in the issue for any additional clues.