Skip to content

Commit 5f5c3f3

Browse files
author
James Healy
authored
Merge pull request #810 from acaire/patch-1
Improve log group mention in README
2 parents a65d342 + 9f9c414 commit 5f5c3f3

File tree

1 file changed

+2
-7
lines changed

1 file changed

+2
-7
lines changed

README.md

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -191,16 +191,11 @@ You’ll find the stack’s metrics under "Custom Namespaces > Buildkite" within
191191

192192
## Reading Instance and Agent Logs
193193

194-
Each instance streams both system messages and Buildkite Agent logs to CloudWatch Logs under two log groups:
195-
196-
* `/var/log/messages` - System logs
197-
* `/var/log/buildkite-agent.log` - Buildkite Agent logs
198-
* `/var/log/docker` - Docker daemon logs
199-
* `/var/log/elastic-stack.log` - Boot process logs
194+
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.
200195

201196
Within each stream the logs are grouped by instance id.
202197

203-
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.
198+
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.
204199

205200
## Customizing Instances with a Bootstrap Script
206201

0 commit comments

Comments
 (0)