search

kumahq / kuma

🐻 The multi-zone service mesh for containers, Kubernetes and VMs. Built with Envoy. CNCF Sandbox Project.
https://kuma.io/install
Apache License 2.0
3.63k stars 331 forks source link

`kumactl dump` to extract troubleshooting information to help debugging #4098

Open lahabana opened 2 years ago

lahabana commented 2 years ago

Description

We very often need a set of configuration to be able to troubleshoot efficiently.

They are usually:

It would be useful to have a tool kumactl dump --mesh [mesh] <--tag [key=value] --name [dp-name] --service [kuma.io/service]> that does this for a list of services. The output should probably be a tar which can be easily shared or attached to bug report.

name and service can be repeated and will show all services/names matching. Tag is a filter and only show dps that have matching tags.

I believe we have all the apis to do this we simply need to implement the tool.

lahabana commented 2 years ago

Triage: tar, for multizone we'd need: #3789 and this tool should be executed from global

johnharris85 commented 2 years ago

I'm building a superset of this functionality that also includes Kong information (for CRE). Maybe I can steal / contribute depending on who gets to it first :p

jakubdyszkiewicz commented 2 years ago

Aside from Kong-specific information that obviously can't be implemented in Kuma, what other Kuma-specific things do you want to support that are not listed in the ticket?

johnharris85 commented 2 years ago

Dumping the logs also. I noticed the ticket says "dpp of interest", sometimes it's the whole mesh we want, or multiple (usually 2) DPPs that are talking to each other. Maybe a selector, or a list, or all options?

lahabana commented 2 years ago

Yes I think that's what happens when no filter is passed.

For the logs I'm half sure. The one thing with what we mention here is that it works from Global for any kind of deployment. As soon as you add things like logs it's becoming harder to do this

github-actions[bot] commented 2 years ago

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

github-actions[bot] commented 2 years ago

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

github-actions[bot] commented 2 years ago

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

github-actions[bot] commented 2 years ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 9 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 6 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 2 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.