-
Notifications
You must be signed in to change notification settings - Fork 22
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
Viewer program #1
Comments
I had no plans like this. JSON is so ubiquitous that there are multitude of tools to handle them. A viewing software would be potentially more work to write and maintain than slog itself. If you do find something working for you, or plan to work on it, please let us know! |
Okay, but there's the general JSON format, then the specific structure of Slog JSON log files... I think I may write a viewing tool myself. We'll see. |
|
So it’s just a thin wrapper over *slog-stream* really? I didn’t know that (had never actually used it, only judged from what you said about it). Fair enough!
… On 1 Dec 2016, at 19:59, Dawid Ciężarkiewicz ***@***.***> wrote:
slog-json does not really define anything that goes into the json. It's entirely up to the user to define time format, logging severyty key and format and so on. There are some defaults, but they are mostly for users that don't really care. bunyan on the other hand is JSON + definition of key-values semantics.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEF3E47fV91Rt1zfwTP2IkGmFx9O4rtks5rDycOgaJpZM4LBzTJ>.
|
|
I could see this becoming the de-facto standard logging format for Slog, if a viewer program were to be provided alongside it. Perhaps one that simply reads from the JSON format, and outputs in the slog-term format, with some basic searching and date-time range capabilities. Is this in your plans?
The text was updated successfully, but these errors were encountered: