The addition of the splicectl get logs command allows a user to easily grab multiple logs according to a specified selector without having to enumerate each one using the kubectl logs command.
Motivation and Context
Grabbing a set of related logs is now much quicker than it was before because it can be done in a single command. I ran the command with the all flag set: splicectl get logs ... --all and the who process took about 10 seconds and grabbed around 60 logs. This is much faster than having to grab each log individually using the kubectl cli.
I also attempted to make the command run faster by doing the api calls and file writes asynchronously, however the tool was quickly rate limited by the kubernetes api which throttled my requests. No speedup is likely to be found so the couple seconds it takes to get multiple logs is likely a lower bound.
This has been manually tested against a live database, the output of this command was compared to the output of the kubectl get logs command and no differences were found.
Screenshots (if appropriate)
Checklist
If the pull request includes user-facing changes, extra documentation is required:
[ ] If the change is user facing, please ensure you add info in one of the Changelog Inclusions sections.
Changelog Inclusions
base feature note
BREAKING note on base feature
Basically whatever formatting we have here, just plain-text
%> command example
next feature
note on next feature
Additions
Added splicectl get logs command, to get multiple logs from kubernetes at once.
Description
The addition of the
splicectl get logscommand allows a user to easily grab multiple logs according to a specified selector without having to enumerate each one using thekubectl logscommand.Motivation and Context
Grabbing a set of related logs is now much quicker than it was before because it can be done in a single command. I ran the command with the all flag set:
splicectl get logs ... --alland the who process took about 10 seconds and grabbed around 60 logs. This is much faster than having to grab each log individually using the kubectl cli.I also attempted to make the command run faster by doing the api calls and file writes asynchronously, however the tool was quickly rate limited by the kubernetes api which throttled my requests. No speedup is likely to be found so the couple seconds it takes to get multiple logs is likely a lower bound.
See DBAAS-5610
Dependencies
How Has This Been Tested?
This has been manually tested against a live database, the output of this command was compared to the output of the
kubectl get logscommand and no differences were found.Screenshots (if appropriate)
Checklist
If the pull request includes user-facing changes, extra documentation is required:
Changelog Inclusions
Additions
splicectl get logscommand, to get multiple logs from kubernetes at once.Changes
Fixes
Deprecated
Removed
Breaking Changes