App service
Services/Kibana

Kibana service

Kibana web interface for exploring, querying, and visualizing data in a linked Elasticsearch service.

Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.

On Wodby

How Kibana runs on Wodby

What Wodby sets up for this Kibana service. It runs the official Elastic image, configured through environment variables set by the manifest.

Linked Elasticsearch

The elasticsearch link is required. It sets:

VariableMeaning
ELASTICSEARCH_HOSTSthe linked Elasticsearch service over plain HTTP
ELASTICSEARCH_USERNAMEthe built-in kibana_system user
ELASTICSEARCH_PASSWORDthe password Wodby generated for that user on the Elasticsearch service

The Elasticsearch service sets the kibana_system password itself after it starts. Nothing has to be configured by hand, and the enrollment-token setup is switched off (INTERACTIVESETUP_ENABLED). Kibana stays unready until Elasticsearch is up and that password is set.

Signing in

  • The web interface is on port 5601, the service's main HTTP endpoint. SERVER_PUBLICBASEURL is set to the service's URL in the environment.
  • People sign in with Elasticsearch users. The built-in superuser is elastic; its password is the password token of the linked Elasticsearch service. kibana_system is a service account and cannot be used to sign in.

What is generated

Three encryption keys are generated once and kept stable across deployments: XPACK_SECURITY_ENCRYPTIONKEY, XPACK_ENCRYPTEDSAVEDOBJECTS_ENCRYPTIONKEY and XPACK_REPORTING_ENCRYPTIONKEY. Replacing them signs users out and makes encrypted saved objects, such as connector secrets, unreadable.

Telemetry is off (TELEMETRY_ENABLED).

Changing configuration

Kibana settings are environment variables on this service in the image's form: the setting name in upper case with dots replaced by underscores. Do not mount a kibana.yml.

Data

Kibana has no volume. Dashboards, data views and other saved objects are stored in the linked Elasticsearch, on its volume.

Check the result

  • GET http://<app service name>:5601/api/status answers 200 when Kibana is ready.
  • "Kibana server is not ready yet" means Elasticsearch is unreachable or the kibana_system password is not set yet: check the Elasticsearch service first.

Overview

Technical profile and packaging

This page shows how Kibana is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.

Service type

App service

Versions

9.5

Ports and protocols

5601/HTTP

Labels

kibana, visualization, observability

Stacks

Use it inside ready-made stacks or your own

These public stacks already include Kibana as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.

Runtime wiring

Reuse connectivity, storage, and runtime defaults

This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.

Endpoints

5601/HTTP

Technical domains

HTTP endpoints from this service can use technical domains with auto-renewed TLS certificates on Wodby.

Service links

These links define which other services can connect to Kibana when it is used inside a stack.