Ability to generate raise GitHub issues with required troubleshooting information.

[vharsh]

trafficstars

Background

Currently it's easy to see volumes & pools & their states(good/bad/etc) but it's not super-easy & super-fast to get to the root cause behind their state to help in faster debugging.

Scope

• Capture relevant troubleshooting information about volume, pools/vg-groups etc & send them as GitHub issue to (say) openebs/openebs repo so that bugs don't get missed and time spent between follow-ups are reduced.

[survivant]

I wanted to add a new feature request for that. It will be useful to be able to collect all the logs for a particular resource and generate a github issue with it / or a .gz file.

suppose that I have a pod stuck at pending because the volume can't mount (could be a zfs issue with the block device, the volume is not umount correctly...), if we could just collect all the right logs, it will save time to get support