Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CloudWatch Logs Not Namespaced #342

Closed
s01ipsist opened this issue Sep 10, 2017 · 2 comments
Closed

CloudWatch Logs Not Namespaced #342

s01ipsist opened this issue Sep 10, 2017 · 2 comments

Comments

@s01ipsist
Copy link

image

We use CloudWatch Logs for a variety of applications, not just BuildKite CI. It would be ideal if the BuildKite logs used a /buildkite (configurable, or default empty for backwards compatibility) Log Group prefix in order to:

  • enhance readability and maintainability
  • allow prefix based IAM permissions for developers

For example AWS CodeBuild uses the /aws/codebuild prefix for Log Groups.
@lox
Copy link
Contributor

lox commented Sep 10, 2017

Makes a lot of sense! Will do. Whilst we are there, any other thoughts on how those logs are grouped?

@s01ipsist
Copy link
Author

Nope. We haven't had cause to actually inspect those logs yet; stuff just works... 👏 👏

toolmantim added a commit that referenced this issue Sep 11, 2017
@toolmantim
Namespace and rename the log groups
f9e154f 
#342

This makes things easier to find, and allows prefix based IAM permissions
@toolmantim toolmantim mentioned this issue Sep 11, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@s01ipsist @lox