This guide is intended to provide guidance on locating and collecting HashiCorp Boundary log outputs for sharing as part of the support issue troubleshooting workflow.
If you are unsure about your Boundary logs, this guide will help you to identify and share them with HashiCorp Technical Support Engineers when working on Boundary issues.
Finding Boundary Logs on Linux Systems
- If Event Logging has been set up in the configuration:
- Logs can be found at the
Path
location set up in the events stanza of your Boundary’s configuration file
For example based on below configuration, Events logs will be stored at /var/log/boundary
:
events {
observations_enabled = true
sysevents_enabled = true
sink "stderr" {
name = "all-events"
description = "All events sent to stderr"
event_types = ["*"]
format = "hclog-text"
}
sink {
name = "obs-sink"
description = "Observations sent to a file"
event_types = ["observation"]
format = "cloudevents-json"
file {
path = "/var/log/boundary"
file_name = "events.ndjson"
}
}
}
- If Event Filtering has not been configured:
- If Events is not configured in your Boundary's configuration, logs will be available at Linux stdout (with errors going to stderr).
- Logs can be collected by running the following command:
sudo journalctl -b --no-pager -u <boundary-process-name> | gzip -9 > "$(hostname)-$(date +%Y-%m-%dT%H-%M-%SZ)-boundary.log.gz"
Other resources: