kibana-streams
elastic/agent-skills
List, inspect, enable, disable, and resync Kibana Streams via REST API.
What is kibana-streams?
Manage Kibana Streams metadata, settings, queries, and lifecycle through the Streams REST API. Use this skill to read stream definitions, ingest/query settings, significant events, and attachments, or to enable, disable, and resync streams.
- List all streams or retrieve a single stream's definition and metadata
- Read stream ingest and query settings, including data retention configuration
- Retrieve queries, significant events, and attachments (dashboards, rules, SLOs) linked to a stream
- Enable, disable, and resync streams via lifecycle APIs
- Support space-scoped operations using `/s/{space_id}/api/streams` paths
How to install kibana-streams
npx skills add https://github.com/elastic/agent-skills --skill kibana-streams- Kibana URL (e.g., https://localhost:5601 or Cloud deployment)
- API key or basic authentication credentials
- read_stream privilege for read operations; manage_stream privilege for lifecycle operations
How to use kibana-streams
- 1.Authenticate using API key or basic auth (configure via elasticsearch-authn skill if needed)
- 2.Use GET /api/streams to list all streams or GET /api/streams/{name} to inspect a specific stream
- 3.Call GET /api/streams/{name}/_ingest or /_query to read ingest and query settings
- 4.Retrieve queries, significant events, or attachments using the corresponding GET endpoints
- 5.For lifecycle changes, POST to /api/streams/_disable, /_enable, or /_resync with kbn-xsrf header; warn user before disabling (data loss risk for wired streams)
Use cases
- Inspect stream configuration and retention policies before making changes
- List all streams in a Kibana instance to understand data organization
- Retrieve significant events or linked dashboards for a specific stream
- Disable or enable streams to manage data flow (with appropriate warnings for data loss)
- Resync streams to refresh their state after configuration changes
- Kibana administrators managing stream lifecycle
- Observability engineers inspecting stream metadata and settings
- DevOps teams automating stream operations via API
kibana-streams FAQ
Stream lifecycle (ingest.lifecycle.dsl.data_retention) controls retention of the stream's data. Failure store lifecycle controls retention of failed documents only. When users ask to set retention, target the stream's main lifecycle unless they explicitly mention the failure store.
Disabling wired streams deletes their data; classic stream data is preserved. Always warn the user and confirm they understand the risk before calling the disable API.
No. This skill covers read operations and lifecycle only (enable, disable, resync). Create, update, delete, fork, and other mutating operations are not yet supported.
Use the space-scoped path /s/{space_id}/api/streams instead of /api/streams for all endpoints.
API key or basic auth. Refer to the elasticsearch-authn skill for authentication setup and configuration.
Full instructions (SKILL.md)
Source of truth, from elastic/agent-skills.
name: kibana-streams description: > List, inspect, enable, disable, and resync Kibana Streams via the REST API. Use when the user needs stream details, ingest/query settings, queries, significant events, or attachments. metadata: author: elastic version: 0.1.0
Kibana Streams
Read stream metadata, settings, queries, significant events, and attachments, and manage stream lifecycle (enable, disable, resync) via the Kibana Streams REST API. Streams are an experimental way to manage data in Kibana — expect API and behavior changes. This skill covers read operations and lifecycle only; create, update, delete, fork, and other mutating operations may be added in a later version.
For detailed endpoints and parameters, see references/streams-api-reference.md.
When to use
- Listing all streams or getting a single stream's definition and metadata
- Reading a stream's ingest or query settings
- Listing a stream's queries
- Reading significant events for a stream
- Listing attachments (dashboards, rules, SLOs) linked to a stream
- Enabling, disabling, or resyncing streams
Prerequisites
| Item | Description |
|---|---|
| Kibana URL | Kibana endpoint (e.g. https://localhost:5601 or a Cloud deployment URL) |
| Authentication | API key or basic auth (see the elasticsearch-authn skill) |
| Privileges | read_stream for read operations; manage_stream for lifecycle APIs |
Use the space-scoped path /s/{space_id}/api/streams when operating in a non-default space. For role configuration
(Kibana feature privileges and Elasticsearch-level permissions), refer to
Streams required permissions.
API base and headers
- Base path:
GETorPOSTto<kibana_url>/api/streams(or/s/<space_id>/api/streamsfor a space). - Read operations: Typically do not require extra headers; follow the official API docs for each endpoint.
- Lifecycle operations:
POST /api/streams/_disable,_enable, and_resyncare mutating — sendkbn-xsrf: true(or equivalent) as required by your Kibana version.
Operations (read + lifecycle)
Read
| Operation | Method | Path |
|---|---|---|
| Get stream list | GET | /api/streams |
| Get a stream | GET | /api/streams/{name} |
| Get ingest stream settings | GET | /api/streams/{name}/_ingest |
| Get query stream settings | GET | /api/streams/{name}/_query |
| Get stream queries | GET | /api/streams/{name}/queries |
| Read significant events | GET | /api/streams/{name}/significant_events |
| Get stream attachments | GET | /api/streams/{streamName}/attachments |
Lifecycle
| Operation | Method | Path |
|---|---|---|
| Disable streams | POST | /api/streams/_disable |
| Enable streams | POST | /api/streams/_enable |
| Resync streams | POST | /api/streams/_resync |
Path parameters: {name} and {streamName} are the stream identifier (same value; the API docs use both names).
Lifecycle and retention (ingest settings)
Ingest settings (GET /api/streams/{name}/_ingest) expose two separate lifecycle areas:
- Stream lifecycle (
ingest.lifecycle) — Controls how long the stream's data is retained. Uselifecycle.dsl.data_retention(e.g."30d") for explicit retention, orlifecycle.inheritfor child streams. This is what users usually mean when they ask to "set retention", "update retention", or "change the stream's retention". - Failure store lifecycle (
ingest.failure_store.lifecycle) — Controls retention of failed documents only (documents that did not process successfully). Users rarely need to change this unless they explicitly mention the failure store or failed-document retention.
When a user asks to set or update retention, target the stream's main lifecycle (lifecycle.dsl.data_retention),
not the failure store, unless they specifically ask about failure store or failed documents.
Examples
List streams
curl -X GET "${KIBANA_URL}/api/streams" \
-H "Authorization: ApiKey <base64-api-key>"
Get a single stream
curl -X GET "${KIBANA_URL}/api/streams/my-stream" \
-H "Authorization: ApiKey <base64-api-key>"
Get stream queries
curl -X GET "${KIBANA_URL}/api/streams/my-stream/queries" \
-H "Authorization: ApiKey <base64-api-key>"
Get significant events or attachments
# Significant events
curl -X GET "${KIBANA_URL}/api/streams/my-stream/significant_events" \
-H "Authorization: ApiKey <base64-api-key>"
# Attachments (dashboards, rules, SLOs linked to the stream)
curl -X GET "${KIBANA_URL}/api/streams/my-stream/attachments" \
-H "Authorization: ApiKey <base64-api-key>"
Disable, enable, or resync streams
# Disable streams (request body per API docs) — deletes wired stream data; warn and confirm before proceeding
curl -X POST "${KIBANA_URL}/api/streams/_disable" \
-H "Authorization: ApiKey <base64-api-key>" \
-H "kbn-xsrf: true" \
-H "Content-Type: application/json" \
-d '{}'
# Enable streams
curl -X POST "${KIBANA_URL}/api/streams/_enable" \
-H "Authorization: ApiKey <base64-api-key>" \
-H "kbn-xsrf: true" \
-H "Content-Type: application/json" \
-d '{}'
# Resync streams
curl -X POST "${KIBANA_URL}/api/streams/_resync" \
-H "Authorization: ApiKey <base64-api-key>" \
-H "kbn-xsrf: true" \
-H "Content-Type: application/json" \
-d '{}'
Check the Streams API operation pages for request/response bodies (e.g. request body for _disable/_enable/_resync if required).
Guidelines
- When the user asks to set or update retention, assume they mean the stream's data retention
(
ingest.lifecycle/lifecycle.dsl.data_retention). Do not change only the failure store retention unless they explicitly ask about the failure store or failed documents. - Other mutating operations (create, update, delete, fork, bulk query management, attachment management, and more) are not supported by this skill. See references/streams-api-reference.md for the full list of deferred operations.
- Disabling streams can lead to data loss for wired streams. The disable API deletes wired stream data (classic stream data is preserved). Before calling disable, warn the user and confirm they understand the risk (and have backed up or no longer need the data).
- Prefer read operations when the user only needs to inspect stream state; use lifecycle APIs when they need to enable, disable, or resync streams.
Related skills
More from elastic/agent-skills and the wider catalog.

kibana-vega
Create custom Vega visualizations with ES|QL data in Kibana dashboards.

observability-edot-dotnet-instrument
Instrument .NET applications with Elastic Distribution of OpenTelemetry for automatic tracing, metrics, and logs.

observability-edot-dotnet-migrate
Migrate .NET applications from classic Elastic APM agent to EDOT .NET SDK

observability-edot-java-instrument
Instrument Java applications with Elastic's OpenTelemetry agent for automatic tracing, metrics, and logs.

observability-edot-java-migrate
Migrate Java applications from classic Elastic APM agent to EDOT Java agent.

observability-edot-python-instrument
Instrument Python apps with Elastic Distribution of OpenTelemetry for automatic tracing, metrics, and logs.