Skip to content

Commit

Permalink
Merge pull request #810 from acaire/patch-1
Browse files Browse the repository at this point in the history
Improve log group mention in README
  • Loading branch information
yob committed Mar 14, 2021
2 parents a65d342 + 9f9c414 commit 5f5c3f3
Showing 1 changed file with 2 additions and 7 deletions.
9 changes: 2 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -191,16 +191,11 @@ You’ll find the stack’s metrics under "Custom Namespaces > Buildkite" within

## Reading Instance and Agent Logs

Each instance streams both system messages and Buildkite Agent logs to CloudWatch Logs under two log groups:

* `/var/log/messages` - System logs
* `/var/log/buildkite-agent.log` - Buildkite Agent logs
* `/var/log/docker` - Docker daemon logs
* `/var/log/elastic-stack.log` - Boot process logs
Each instance streams file system logs such as `/var/log/messages` and `/var/log/docker` into namespaced AWS Log Groups. A full list of files and log groups can be found in the relevant [Linux](https://github.com/buildkite/elastic-ci-stack-for-aws/blob/master/packer/linux/conf/awslogs/awslogs.conf) `awslogs.conf` file.

Within each stream the logs are grouped by instance id.

To debug an agent first find the instance id from the agent in Buildkite, head to your [CloudWatch Logs Dashboard](https://console.aws.amazon.com/cloudwatch/home?#logs:), choose either the system or Buildkite Agent log group, and then search for the instance id in the list of log streams.
To debug an agent, first find the instance id from the agent in Buildkite, head to your [CloudWatch Logs Dashboard](https://console.aws.amazon.com/cloudwatch/home?#logs:), choose the desired log group, and then search for the instance id in the list of log streams.

## Customizing Instances with a Bootstrap Script

Expand Down

0 comments on commit 5f5c3f3

Please sign in to comment.