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

Create and distribute a diagnostics tool #1331

Closed
zgramana opened this issue Dec 8, 2015 · 6 comments
Closed

Create and distribute a diagnostics tool #1331

zgramana opened this issue Dec 8, 2015 · 6 comments
Assignees
Milestone

Comments

@zgramana
Copy link
Contributor

zgramana commented Dec 8, 2015

Looking for an equivalent of cbcollect_info.

@zgramana zgramana self-assigned this Dec 8, 2015
@zgramana zgramana added this to the 1.2.0 milestone Dec 8, 2015
@zgramana
Copy link
Contributor Author

zgramana commented Dec 8, 2015

Currently re-purposing cbcollect_info as sgcollect_info.

@mattcarabine
Copy link
Contributor

In support, we use tools to automatically parse cbcollect_infos, it would be very nice to be able to do this for sgcollect_infos too, as you are repurposing the system level information from cbcollect this should be possible.

I just have one ask and that is to easily be able to identify if the zip file if an sgcollect_info or a cbcollect_info, just something like 'sync gateway logs' at the top of one of the files would be great.

@b33f
Copy link

b33f commented Jan 11, 2016

cbcollect_info is also a moving target, would it be possible to have a shared library between sgcollect_info and cbcollect_info so that updates to system stats in one get reflected in the other ?

@mattcarabine
Copy link
Contributor

I realise my previous was very poorly defined, something along the lines of renaming couchbase.log (the main system level information) to sync_gateway.log would be fantastic. It means we can determine whether or not a zip file is a cbcollect or an sgcollect without even having to open and parse any of the contained files.

@zgramana zgramana modified the milestones: 1.2.0, 1.3 Feb 17, 2016
@zgramana
Copy link
Contributor Author

@mattcarabine good point. This is a WIP, so nows the time to throw in requests. :)

@b33f this is a good idea. The system tasks code alone would be very useful to have on PIP. The S3, CBSE tagging stuff, etc., probably not so much, but still a prime candidate for a module.

@tleyden
Copy link
Contributor

tleyden commented Mar 24, 2016

Closing as a dupe of #1640

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants