Document all the logs that we can retrieve and where to pull
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
We have a reference on where to pull kubelet logs here: https://anywhere.eks.amazonaws.com/docs/troubleshooting/troubleshooting/#kubectl-commands-return-dial-tcp-io-timeout
But these logs as well as other logs should be referenced in one area so customers know where to be able to pull logs based on specific information as a reference point. We do have https://repost.aws/knowledge-center/eks-anywhere-check-component-logs, but that is not integrated in our documentation.
Contributor guide
Research direction
Start with the existing kubelet log reference and the AWS re:Post component-logs article linked in the issue. Identify the logs customers may need and consolidate their retrieval locations in one documentation area, integrating the existing guidance. Done means the relevant log sources and where to pull them are documented together.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation, observability
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100