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

Add command logging support #45

Open
lowell80 opened this issue Feb 28, 2019 · 0 comments
Open

Add command logging support #45

lowell80 opened this issue Feb 28, 2019 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@lowell80
Copy link
Member

All CLI calls should be (optionally) logged to a central log file. For the Splunk app install, this should be easy enough ($SPLUNK_HOME/var/log/splunk/ksconf-exec.log, or something like that.) But for standard installs this needs to be thought through more.

The log format should be single-line JSON objects.

Needs props.conf entry and possibly a simple search / dashboard.

Need to make sure we can easily globally disable this for things like unittesting.

Long term this could be helpful for capturing what commands and arguments are most frequently used. Possibly with an easy way for users to anonymize and submit some aggregate usage data (opt-in only, of course).

@lowell80 lowell80 added the enhancement New feature or request label Feb 28, 2019
@lowell80 lowell80 added this to the Release 0.9.0 milestone Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant