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.

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

Document suggested/example remote logging facility #29

Open
otterley opened this issue Mar 12, 2020 · 5 comments
Open

Document suggested/example remote logging facility #29

otterley opened this issue Mar 12, 2020 · 5 comments
Labels
blog-post Should be addressed by a blog post rather than documentation

Comments

@otterley
Copy link

We need a way to send system log streams for the kernel and all user-space components to external log collectors in real time.

For the EC2 AMI, we need to make it easy to stream logs to CloudWatch Logs.

Support for other log collectors can be added as well - it would be useful for interested users to indicate their preferences here and vote on them.

@zmrow
Copy link

zmrow commented Mar 16, 2020

We have no current plans to add a logging agent to the host OS.

When talking with many EKS customers, we found that a common pattern is to use Kubernetes’ facilities for log streaming, even for system level logs. Another method is to use Fluent Bit as covered in this blog post. These are our suggested methods for customers to get both container logs as well as other logs off the box.

@otterley
Copy link
Author

@zmrow I agree that it doesn't necessarily need to be in the host OS per se. Consider this a recommendation to add some documentation/examples to enable the functionality for those who need it.

@zmrow zmrow changed the title Need remote logging facility Document suggested/example remote logging facility Mar 16, 2020
@gabegorelick
Copy link

I think the particulars about remote logging are less important than documenting what to log. In other words, it would be useful to have a reference of where notable log files live. Something that says "the journal is available at /var/log/journal, /var/log/messages doesn't exist, container logs are available at /var/log/containers/*.log, etc."

Especially with host containers, it can be hard to figure out where something like the admin container's ssh logs live (is it mounted on the host somewhere, or do we have to enter the container to get it?).

@stmcginnis
Copy link
Contributor

@stockholmux can we get this issue transferred to the project-website repo to track the work there?

I think it would be useful to document how to create and deploy a logging and metrics host container as part of the overall docs.

Another option would be to have a blog post similar to https://aws.amazon.com/blogs/opensource/centralized-container-logging-fluent-bit/, but I think this comes up often enough that it would be useful to have it right in the docs.

@stockholmux
Copy link
Member

Works for me @stmcginnis

@stockholmux stockholmux transferred this issue from bottlerocket-os/bottlerocket Feb 14, 2023
@stockholmux stockholmux added the blog-post Should be addressed by a blog post rather than documentation label Feb 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blog-post Should be addressed by a blog post rather than documentation
Projects
None yet
Development

No branches or pull requests

5 participants