Configure Telemetry, Logs, Metrics & SSL in Kestra
For the complete documentation index, see llms.txt. For a full content snapshot, see llms-full.txt. Append.mdto anykestra.io/docs/*URL for plain Markdown.
Use this page for operational visibility and network-facing configuration.
Observability
Use this section when you need to understand what Kestra emits about itself, not when you are changing task behavior. The settings here are mostly for platform operators and anyone integrating Kestra with monitoring or logging systems.
Configuration areas in this group include:
- anonymous telemetry
- logger settings
- access logs and log formatting
- metrics and label-based metrics
- Micronaut HTTP settings
These settings are useful when you need to tune visibility, log volume, request handling, or integration with monitoring platforms.
Anonymous usage reporting is enabled by default. Disable or tune it with:
yamlkestra:
anonymous-usage-report:
enabled: falseyamlkestra:
anonymous-usage-report:
initial-delay: 5m
fixed-delay: 1hUI usage reporting is configured separately:
yamlkestra:
ui-anonymous-usage-report:
enabled: falseLogs and access logging
There are two different concerns here: application logs and HTTP access logs. Reach for logger.levels when you want to change verbosity inside Kestra, and Micronaut access logging when you want request-by-request HTTP visibility.
Use logger.levels to adjust server log verbosity:
yamllogger:
levels:
io.kestra.core.runners: TRACE
org.apache.kafka: DEBUGYou can also suppress execution-scoped logs globally:
yamllogger:
levels:
execution: 'OFF'
task: 'OFF'
trigger: 'OFF'Or scope suppression to a specific flow, task, or trigger by appending the flow ID and optionally the task or trigger ID:
yamllogger:
levels:
execution.hello-world: 'OFF'
task.hello-world: 'OFF'
trigger.hello-world: 'OFF'
task.hello-world.log: 'OFF'
trigger.hello-world.schedule: 'OFF'Micronaut access logging is configured separately:
yamlmicronaut:
server:
netty:
access-logger:
enabled: true
logger-name: io.kestra.webserver.access
log-format: "[Date: {}] [Duration: {} ms] [Method: {}] [Url: {}] [Status: {}] [Length: {}] [Ip: {}] [Port: {}]"
exclusions:
- /ui/.+
- /health
- /prometheusKestra uses Logback for logging. To use a custom logback.xml, pass it via JAVA_OPTS:
shellexport JAVA_OPTS="-Dlogback.configurationFile=file:/path/to/logback.xml"GCP structured logging:
xml<?xml version="1.0" encoding="UTF-8"?>
<configuration debug="false">
<include resource="logback/base.xml" />
<include resource="logback/gcp.xml" />
<root level="WARN">
<appender-ref ref="CONSOLE_JSON_OUT" />
<appender-ref ref="CONSOLE_JSON_ERR" />
</root>
</configuration>ECS format:
xml<?xml version="1.0" encoding="UTF-8"?>
<configuration debug="true">
<include resource="logback/base.xml" />
<include resource="logback/ecs.xml" />
<root level="WARN">
<appender-ref ref="CONSOLE_ECS_OUT" />
<appender-ref ref="CONSOLE_ECS_ERR" />
</root>
</configuration>Metrics and telemetry exports
These settings are usually enabled with restraint. Metrics are broadly useful, but label-based metrics should stay limited to a small set of low-cardinality dimensions or they become expensive to store and query.
Set a metrics prefix:
yamlkestra:
metrics:
prefix: kestraAdd low-cardinality labels as metric tags:
yamlkestra:
metrics:
labels:
- country
- environmentThis creates a tag named label_<key> for each configured label. When an execution does not have a configured label key, the tag value is set to __none__, which keeps the set of tag keys stable and avoids metric series fragmentation.
For example, with country and environment configured, an execution that has country=Germany but no environment label produces:
plaintextkestra_executions_total{flow_id="my-flow",namespace_id="default",state="SUCCESS",label_country="Germany",label_environment="__none__"} 1For traces, metrics, and logs exported through OpenTelemetry, use the dedicated OpenTelemetry guide.
Network and HTTP settings
This section matters when Kestra is exposed behind a load balancer, reverse proxy, ingress, or private network boundary. If requests are not arriving with the expected URL, protocol, size limit, or auth behavior, the fix is often here.
Micronaut-backed settings cover:
- server port
- SSL
- timeouts
- upload size
- base path
- host resolution
- CORS
- management endpoints
Common examples:
yamlmicronaut:
server:
port: 8086yamlmicronaut:
server:
max-request-size: 10GB
multipart:
max-file-size: 10GB
disk: true
read-idle-timeout: 60m
write-idle-timeout: 60m
idle-timeout: 60m
netty:
max-chunk-size: 10MBReverse proxy support:
yamlmicronaut:
server:
context-path: "kestra-prd"
host-resolution:
host-header: Host
protocol-header: X-Forwarded-ProtoEnable CORS:
yamlmicronaut:
server:
cors:
enabled: trueSecure or move management endpoints:
yamlendpoints:
all:
basic-auth:
username: your-user
password: your-password
port: 8084SSL example:
yamlmicronaut:
security:
x509:
enabled: true
ssl:
enabled: true
server:
ssl:
client-authentication: need
key-store:
path: classpath:ssl/keystore.p12
password: ${KEYSTORE_PASSWORD}
type: PKCS12
trust-store:
path: classpath:ssl/truststore.jks
password: ${TRUSTSTORE_PASSWORD}
type: JKSUI and webserver settings
These settings are lighter-weight than the Micronaut server settings above. Use them when you are customizing the user-facing web experience rather than transport-level HTTP behavior.
The webserver-related configuration also includes:
- Google Analytics ID
- additional HTML tags
- mail server settings
Examples:
yamlkestra:
webserver:
google-analytics-id: G-XXXXXXXXXXyamlkestra:
webserver:
html-head:
- "<script>/* custom tag */</script>"Mail server settings are useful when you need platform emails for invitations and notifications.
Default time range for charts
kestra.ui.charts.default-duration sets the time range the UI applies when you haven't selected one: on dashboards, on the flow and namespace overview charts, and on lists that filter by date. It takes an ISO 8601 duration and defaults to PT24H. For example, to show the last 7 days by default:
yamlkestra:
ui:
charts:
default-duration: P7DTypical use cases
Use this section when you need to:
- expose Kestra behind a reverse proxy
- enable HTTPS
- adjust access log format for GCP or ECS
- configure Prometheus-style metrics ingestion
- change management endpoint behavior