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

Extend the Troubleshooting document with how and what logs should be collected #1929

Open
brianehlert opened this issue May 2, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@brianehlert
Copy link

brianehlert commented May 2, 2024

When a customer needs support, there is a set of logs or configurations that are necessary to aid the person providing support.
The troubleshooting document should include a list of useful data points to collect and outline how to collect those.

Such as:

  • situation x - this is how you deeply inspect a resource to see its events and full status
  • situation y - this is how to retrieve NGINX logs, controller logs, etc.
  • situation z - this is how to retrieve logs from a pod that had been killed.
@brianehlert brianehlert added the enhancement New feature or request label May 2, 2024
@nginx-bot nginx-bot bot added the community label May 2, 2024
@sjberman sjberman added documentation Improvements or additions to documentation and removed enhancement New feature or request community labels May 6, 2024
@nginx-bot nginx-bot bot added the community label May 8, 2024
@lucacome lucacome removed the community label May 9, 2024
@nginxinc nginxinc deleted a comment from nginx-bot bot May 9, 2024
@mpstefan mpstefan added this to the v1.3.0 milestone May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: 🆕 New
Development

No branches or pull requests

4 participants