Skip to content

Limitations

github-actions[bot] edited this page Nov 13, 2026 · 6 revisions

Limitations

Elastic behaviors elkctl cannot change, each with what the tool does about it.

Some features need Kibana 9.5.1 or newer

Dashboards, exception lists, Fleet policies, prebuilt rules, and rule source scoping need Kibana 9.5.1 or newer, the oldest version with complete recorded evidence. Rule source scoping is any --source other than all, which includes the state default, custom.

Against an older stack, these commands answer unsupported before the feature's first request. The message names the feature, the flavor, the reported version, and the 9.5.1 floor. Rule commands that read every source work, and local commands such as validate never check the version. In MCP, stack_info and stack_doctor stay usable for diagnosing an older stack.

An organization-level Cloud key is not supported

Use a project- or deployment-scoped Elasticsearch API key created inside Kibana. An organization-level Elastic Cloud API key behaves differently by flavor:

  • Serverless 9.7.0 accepts it for reads and for CLI rule changes, including an enable. Older Serverless versions may refuse to enable a rule with it, because the alerting framework would not create a rule API key for it.
  • Hosted refuses it when it authenticates.
  • MCP planning refuses it on every flavor with credential_unsuitable: it reaches the whole organization and its role scope cannot be read, so a plan cannot show what it may do.

The essu_ prefix does not tell the key types apart. elkctl doctor reports the realm the key authenticates through: _cloud_api_key is an organization-level key and gets a warning, and _es_api_key is a scoped key. See which key to use.

Serverless tags a rule enabled by a project-scoped key

On Serverless 9.7.0, enabling a rule with a project-scoped key appends the tag Missing Elastic Cloud API Key to the rule. The rule still runs. elkctl treats the tag as server-applied state: state pull never writes it, state diff does not report it, and state push never sends it. A rule cannot keep this exact tag through the mirror; a rule file that carries it reads as if it did not. rules get and rules export omit it as well; rules list shows it.

Rule search cannot reach description or query

The public rules API cannot filter on a rule's description or query; a filter on either answers 400. rules list --search therefore matches a name substring, ignoring case, or an exact tag. To find text inside a rule's query or description, pull or export the rules and search the files. See Rules.

Reading more than 10,000 rules

A single rule search returns at most 10,000 results, however it pages. rules list and state read a larger corpus as one search per rule type, split again by enabled state when one type passes the limit, and refuse the read when the parts do not add up to the total. A part still above the limit answers unsupported; narrow the selection with a filter or a tag.

The server's rule export is capped at 10,000 rules and refuses a larger export with a 400. Narrow rules export with selectors, --tag, or --source.

Coverage reads at most 4,000 rules

A rule search returns each rule's full definition; one response for 2,263 rules measured about 19 MB, above the 16 MiB response cap. MCP detection_coverage therefore reads matching rules in 500-rule pages sorted by creation time and checks that no rule is missing or repeated. It accepts at most 4,000 matching rules; a larger match fails with unsupported. Narrow it with enabled, source, or tag. If the rules change during the read, it reads once more, and a second change fails the call with conflict; retry it.

Each 500-rule page is about 4.4 MB. Over a slow link, one pass over 4,000 rules can take more than 20 seconds and a second pass more than 40, past the 30-second default deadline. Start the server with a longer --timeout, up to 120 seconds, when the matching corpus is near the limit.

A rule over a missing index reports partial failure

When a rule's index patterns match no index, Kibana records its last execution as partial failure, not failed. Prebuilt rules for data the deployment does not collect often show it. MCP rule_health reports last_execution_partial_failure for this status, and alert_context reports rule_last_execution_failed only for failed. rule_readiness shows which patterns match.

Prebuilt rule install takes no selection

The public install route installs every missing prebuilt rule and updates every outdated one in one call. It accepts no selection and has no dry-run option. rules prebuilt install computes its preview from the prebuilt status counts and, with --yes, applies the whole pack. There is no per-rule upgrade.

Rule preview returns no hit count

The preview route reports errors and warnings but not how many events matched. rules preview reads the matches back from the preview alerts index with the preview's id, and retries once after one second when the first read finds none. If that read fails, the preview still reports its errors and warnings, with hits null and the failure in hits_error.

Older versions cannot read a value-list mirror

elasticctl 0.9 reads only rules/ and exceptions/ in a state directory. 0.9.4 refuses state pull, state diff, and state push on a directory that holds value-lists/, and names 0.10 as the version that reads it. 0.9.0 to 0.9.3 cannot be changed: they push such a directory's exceptions without its value lists, leaving stale values on the stack, and a pull into it leaves its value lists stale. Use 0.10 or later, and at least 0.9.4 anywhere an older binary may still run. See Rules as Code.

Some value lists suppress every event

On Kibana 9.5.1, 9.5.6, and 9.7.0, an exception on a value list suppresses every event when:

  • the list exists and is empty, under is in list;
  • it is an ip_range list that stores more than 200 values in dash form (a-b), with either operator.

A missing list under is not in list also suppresses every event that has the field. elkctl refuses any write that would cause one of these, and writes a single address as CIDR, which does not count toward the 200. See Value Lists.

Value-list writes are not locked or immediate

Kibana has no lock on a value list, does not change a list's version when its values change, and applies a value import some time after it answers. elkctl checks each change by reading the list back, and a list it cannot confirm within 120 seconds ends unknown. Coordinate writers outside elkctl, and read When the outcome is unknown before you retry.

Alerts cannot be deleted

The public API has no alert delete. Close alerts with alerts close instead. Cases can be deleted with cases delete.

A Kibana space does not restrict Elasticsearch

Spaces scope Kibana objects: rules, exception lists, data views, dashboards, alerts, and cases. Elasticsearch index access follows the credential. search and the MCP query tools read every index the API key can read, whatever --space says. Limit access with the key's privileges. See Search.

Index pattern checks need the Elasticsearch URL

MCP rule_readiness resolves a rule's index patterns on Elasticsearch, with _resolve/index, not through Kibana. When the profile has no Elasticsearch URL, it skips the patterns part with not_configured and still reports the data view and integrations. Set the URL with ELASTICCTL_ES_URL or in the profile; see Configuration.

Assigning a user needs a Kibana user profile

Alert and case assignees are user profile ids, and a profile exists only after the user has logged in to Kibana once. An API key identity never has one.

elkctl resolves a username to its profile and matches it exactly. No match is not_found, and several matches are conflict. On Hosted and self-managed stacks the lookup uses the Elasticsearch user profile API, which needs the read_security privilege and, on Hosted, the Elasticsearch URL in the profile. Serverless answers that API with 410, so elkctl uses the Security solution's own route there. When the lookup route is unavailable the command answers unsupported; pass uid:<profile_uid> to skip the lookup.

Kibana deletes a referenced data view

Kibana deletes a data view even while dashboards refer to it, and leaves those dashboards broken. data-views delete refuses a referenced data view unless --replace-with moves its references first. See Data Views and Dashboards.

Legacy scripted fields

Serverless drops a data view's legacy scripted fields, while Hosted and self-managed stacks keep them. Because they do not survive every stack, a portable data-view file carrying them is rejected before any request.

Some dashboard content does not round-trip

The typed Dashboards API leaves out content it cannot represent and returns a warning instead. dashboards export refuses a dashboard whose response carries warnings, names each one, and points to dashboards bundle export, which moves the dashboard as an opaque Saved Objects bundle.

Kibana also accepts a root time_range.mode on write but does not store it. dashboards import rejects a file carrying that field before any change.

Clone this wiki locally