Skip to content
Distr
Star
Book DemoStart free trialLogin

Data Sent to Distr

DataWhen
Controller logs at debug level, including connection events, reconciliation cycles, errors and the output of Docker and Helm operationsAlways
The status of every deployment, whose message can contain the Compose progress, the Helm output, image names and error outputAlways
stdout and stderr of the containers of the deploymentsWhen log collection is enabled
Docker: CPU, memory and disk usage of the host with the device names and mount paths, the size of the image store and the CPU, memory, limits and log size of every container of the deploymentsWhen metrics are enabled
Kubernetes: CPU and memory capacity and usage summed over all nodes, the usage of the controller pod and the CPU, memory and limits of every container of the deployments with its pod and workload namesWhen metrics are enabled

The controller reads no logs or metrics of containers outside its deployments apart from its own. Distr masks the secrets of the deployment target and common credential patterns in logs before it stores them, see Log Redaction. Status messages are stored as reported.

Log collection and metrics are settings of the deployment target, see the Configuration Reference.

Example Controller Logs

Section titled “Example Controller Logs”

These lines are taken from the controller logs of a Kubernetes and a Docker deployment target, as Distr shows and exports them. Every line has the time, the level, the place in the controller’s code, the message and the fields of the message. Lines written by Helm carry "component": "helm" instead of a place in the code. The container logs of the deployments are not part of the controller logs.

2026-11-09T14:33:26Z  info  kubernetes/main.go:243  controller version has changed. starting self-update
2026-11-09T14:33:28Z  info  kubernetes/main.go:265  self-update has been applied
2026-11-09T14:45:04Z  info  kubernetes/main.go:105  kubernetes controller is starting  {"version": "4.9.0-rc.1", "commit": "278beaa", "release": true}
2026-11-09T14:45:09Z  info  controllerclient/client.go:193  token has expired or is about to expire
2026-11-09T14:45:10Z  info  controllerclient/client.go:202  token refreshed
2026-11-09T15:52:10Z  debug  kubernetes/main.go:239  controller version is up to date
2026-11-09T15:52:11Z  debug  kubernetes/metrics.go:47  node metrics  {"node": "minikube", "cpuUsage": 713, "memUsage": 1690030080}
2026-11-09T15:52:12Z  debug  getting release history  {"component": "helm", "name": "production-cluster-3"}
2026-11-09T15:52:13Z  debug  kubernetes/logs.go:130  get logs for resource  {"deploymentId": "8c8f78c9-e628-469f-a0c6-6da8bbd2767b", "resourceKind": "Deployment", "resourceName": "production-cluster-podinfo", "sinceTime": "2026-11-09T15:51:41.262Z"}
2026-11-09T15:52:16Z  debug  kubernetes/status_check.go:181  checking status  {"resourceKind": "Deployment", "resourceNamespace": "llm-1", "resourceName": "production-cluster-podinfo"}
2026-11-09T15:52:16Z  info  controllerclient/client.go:89  reporting deployment status  {"deploymentId": "8c8f78c9-e628-469f-a0c6-6da8bbd2767b", "revisionId": "4de6d2d2-7f10-47cb-92c8-9aef453fb29c", "type": "healthy", "message": "status check passed. 2 resources healthy"}
2026-11-09T15:52:17Z  debug  deploymentlogs/collector.go:70  skipped flushing log records  {"deploymentId": "6a9796e8-94c7-4873-9a45-c835bdeaf5e0", "logRecords": 0, "resourceNames": []}

A controller writes most of these lines on every cycle. The two deployment targets these lines come from have two deployments each, and their controller logs grew by about 5,000 lines per hour on Docker and 14,000 on Kubernetes.