Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

weave status can contain large amounts of output #1025

Closed
awh opened this issue Jun 26, 2015 · 5 comments · Fixed by #1248
Closed

weave status can contain large amounts of output #1025

awh opened this issue Jun 26, 2015 · 5 comments · Fixed by #1248
Assignees
Labels
Milestone

Comments

@awh
Copy link
Contributor

awh commented Jun 26, 2015

The lists of MACs, peers, retries, routes, allocated ranges and DNS registrations can all get very big. Perhaps we should print a summary only, and then have flags or dump commands that list out these different quantities in full (preferably in machine readable form).

@awh awh added the feature label Jun 26, 2015
@rade
Copy link
Member

rade commented Jun 26, 2015

I've been thinking the same. In particular it would be good if the default status output was more of a "health status", i.e. something from which it is quite easy to tell whether everything is alright or not (and why not).

re machine-readable form - that's what we have the (undocumented) json output for.

@bboreham
Copy link
Contributor

When troubleshooting weave it would be nice to be able to get full information; for instance there is no way currently to get a full dump of what the IPAM Allocator thinks.

We could have options on status, e.g. short/tall/grande/venti.

@awh
Copy link
Contributor Author

awh commented Jun 26, 2015

In particular it would be good if the default status output was more of a "health status"

Referencing #908.

@awh
Copy link
Contributor Author

awh commented Jun 26, 2015

(undocumented) json output

Raised #1027.

@rade rade modified the milestone: current Jul 7, 2015
@awh awh self-assigned this Jul 14, 2015
@awh
Copy link
Contributor Author

awh commented Jul 15, 2015

Referencing #1141.

@awh awh closed this as completed in #1248 Aug 11, 2015
awh added a commit that referenced this issue Aug 11, 2015
@rade rade modified the milestones: current, 1.1.0 Aug 12, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants