Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Tarmak export logs command #574

Closed
JoshVanL opened this issue Oct 12, 2018 · 0 comments · Fixed by #575
Closed

Tarmak export logs command #574

JoshVanL opened this issue Oct 12, 2018 · 0 comments · Fixed by #575
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@JoshVanL
Copy link
Contributor

JoshVanL commented Oct 12, 2018

/kind feature

What happened:
Often when debugging with someone remotely it is difficult to ensure all logs of interested are collected. This can lead to missing something or increasing the debug loop time to find the problem/solution.

What you expected to happen:
Tarmak should provide a command that goes and fetches the logs which can then be bundled together in a consistent way. This should be done by SSHing into all relevant instances, grabbing journald into a file. Bundle all these files into a tar ball for the user. Exports we should support (not complete):
tarmak cluster logs vault - includes consul cluster and helpers
tarmak cluster logs etcd - includes backups etc
tarmak cluster logs worker - kubelet etc..
tarmak cluster logs master - api server etc..

/assign

@jetstack-bot jetstack-bot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 12, 2018
@JoshVanL JoshVanL mentioned this issue Oct 12, 2018
2 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants