-
Notifications
You must be signed in to change notification settings - Fork 46
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
New command to read accesslogs of an application #360
Comments
Do we have an idea of the format people expect for such kind of things? We do have a lot of details in Warp10. |
CLF support seems a good option (https://en.wikipedia.org/wiki/Common_Log_Format) for starters |
I'm working on a PR for this. Here are the formats and defaults for before / after I went with: Formatssimple
extended
clf
json
A user can always pick the Defaults for before/after
Any thoughts about this? |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now that accesslogs are available to the users in Warp10, we could add a command in clever-tools to make this easier.
It would need to first get a Warp10 token from the API and then query Warp10.
About the API, I guess something like this would be fine:
clever accesslogs --since <date> --until <date> --limit <number>
clever accesslogs --follow
(-f
for short)The follow feature may not be that useful and may not be so trivial to implement without dumping multiple-seconds batches all at once in the console, so I'm not sure that we should do it, not at first at least. The actually useful feature is the since/until one, it seems to me.
The text was updated successfully, but these errors were encountered: