Serving: Feature Request: Create debug configmap and log dump tool

[dgerd]

In what area(s)?

/area API
/area autoscale
/area build
/area monitoring
/area networking
/area test-and-release

Describe the feature

To debug an issue you typically need to:

• Look at Config/Revision/Route status for the Service(s) you care about
• Look for errors in logs of all the different controllers
• Look at what has changed/is set in the Knative ConfigMaps
• Look at the Kubernetes cluster version

It would be really nice to have a tool that takes all of this information and dumps in either on the console or to a file where you can easily search through and find the relevant information you cafe about. This would save manually executing a bunch of kubectl commands to describe/search and dump out information one step at a time.

Such a tool could be useful as well to help others attempt to reproduce reported problems.

[nimakaviani]

inspired by this issue and having to debug my own knative services I wrote Knative-Inspect:

Github Repo: https://github.com/nimakaviani/knative-inspect

very early version with rough edges, but would love to hear if people find it useful or if it can be improved in any way.

[markusthoemmes]

Woah, I love the tree view @nimakaviani! The diff view on the configMap looks brilliant as well. Great job <3

[nimakaviani]

thanks @markusthoemmes!

[mattmoor]

That's super cool. I wonder if we should start to at least link, but potentially gather projects like this and @n3wscott's graph and other tools in a place where folks can more readily discover them?

[jonjohnsonjr]

I wonder if we should start to at least link, but potentially gather projects like this and @n3wscott's graph and other tools in a place where folks can more readily discover them?

I often see this kind of stuff collected into an awesome list. Perhaps knative/awesome?

[knative-housekeeping-robot]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle stale.
Stale issues rot after an additional 30 days of inactivity and eventually close.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle stale

[knative-housekeeping-robot]

Stale issues rot after 30 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle rotten.
Rotten issues close after an additional 30 days of inactivity.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle rotten

[knative-housekeeping-robot]

Rotten issues close after 30 days of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh by adding the comment /remove-lifecycle rotten.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/close

[knative-prow-robot]

@knative-housekeeping-robot: Closing this issue.

In response to this:

Rotten issues close after 30 days of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh by adding the comment /remove-lifecycle rotten.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.