Logging can help you understand what's happening under the hood of your Coder deployment and is useful for debugging and monitoring the health of your cluster.
This article walks you through the configuration options available in the Coder Helm chart.
You can access your logs at any time by running:
kubectl -n coder logs <podname>
The following sections show how you can change your Helm chart values to export logs.
See our guide to updating your Helm chart if you're unfamiliar with updating a Helm chart.
Please note that:
Setting either the
/dev/stderr value to an empty string to
You can use
/dev/stderr interchangeably, since both write
to the pod's standard output and error directories.
Coder supports writing logs to multiple output targets.
This is the default value that's set in the Helm chart:
logging: human: /dev/stderr
When set, logs will be sent to the
/dev/stderr file path and formatted for
You can get JSON-formatted logs by setting the
logging: json: /dev/stderr
If you deployed your Kubernetes cluster to Google Cloud, you can send logs to Stackdriver:
logging: stackdriver: /dev/stderr
Coder can send logs directly to Splunk. Splunk uses the HTTP Event Collector (HEC) to receive data and application logs. See Splunk's docs for information on configuring an HEC.
Once you've configured an HEC, you'll need to update your Helm chart with your HTTP (HEC) endpoint and your HEC collector token.
To provide your HTTP (HEC) endpoint:
logging: splunk: url: ""
To provide your HEC collector token:
logging: splunk: token: ""
Optionally, you can specify the Splunk channel. that you'd like associated with your messages. Channels allow logs to be segmented by client, preventing Coder application logs from affecting other client logs in your Splunk deployment.
logging: splunk: channel: ""