cf-dev@lists.cloudfoundry.org | Logs, Timestamps

Home Messages Hashtags Subgroups

Date Date 1 - 3 of 3

Logs, Timestamps

Daniel Jones #2485 Hi all, Why are logs like those of the CloudController dated by machine-readable timestamps? Are there any tools to parse CF logs in-situ? I find it a constant source of frustration trying to debug an issue reported by a human with a human-parseable date, putting that into a Unix timestamp converter, searching through logs for that timestamp, then scrolling up and down having to occasionally copy/paste a timestamp back into a converter to see if I've gone too far away from my rough target time. Computers are rather good at converting data formats - my brain, not so much. Wouldn't it make more sense to have the logs human-readable by default, and if an automated system needs to ingest those logs, let it do the parsing? Regards, Daniel Jones EngineerBetter.com attachment.html
More All Messages By This Member
Bharath #2486 Hi daniel , The logs formats are basically using log library called steno https://github.com/cloudfoundry/steno It was mentioned that we can configure to modify the logs to a human readable format. I never did that . I think you can have a look into it you can also look at firehouse and nozzles project . I think that is also use ful http://docs.cloudfoundry.org/loggregator/architecture.html#firehose http://docs.cloudfoundry.org/loggregator/architecture.html#nozzles tutorials on nozzle http://docs.cloudfoundry.org/loggregator/nozzle-tutorial.html regards Bharath On Wed, Oct 28, 2015 at 2:06 PM, Daniel Jones < daniel.jones(a)engineerbetter.com> wrote: Hi all, Why are logs like those of the CloudController dated by machine-readable timestamps? Are there any tools to parse CF logs in-situ? I find it a constant source of frustration trying to debug an issue reported by a human with a human-parseable date, putting that into a Unix timestamp converter, searching through logs for that timestamp, then scrolling up and down having to occasionally copy/paste a timestamp back into a converter to see if I've gone too far away from my rough target time. Computers are rather good at converting data formats - my brain, not so much. Wouldn't it make more sense to have the logs human-readable by default, and if an automated system needs to ingest those logs, let it do the parsing? Regards, Daniel Jones EngineerBetter.com attachment.html
More All Messages By This Member
Guillaume Berche #2540 The steno-prettify tool may be given a try to format timestamps in human readeable dates on the vm itself . See doc I contributed at [1] for sample invocation in-situ on the vm. I haven't tested in a while, let me know if this still works or doc needs update (the procedure had been broken a while ago [2] Hope this helps, Guillaume. [1] http://docs.cloudfoundry.org/running/troubleshooting.html#failing-job [2] https://github.com/cloudfoundry/docs-running-cf/pull/7 toggle quoted messageShow quoted text Le 28 oct. 2015 09:58, "Bharath Posa" <bharathp(a)vedams.com> a écrit : Hi daniel , The logs formats are basically using log library called steno https://github.com/cloudfoundry/steno It was mentioned that we can configure to modify the logs to a human readable format. I never did that . I think you can have a look into it you can also look at firehouse and nozzles project . I think that is also use ful http://docs.cloudfoundry.org/loggregator/architecture.html#firehose http://docs.cloudfoundry.org/loggregator/architecture.html#nozzles tutorials on nozzle http://docs.cloudfoundry.org/loggregator/nozzle-tutorial.html regards Bharath On Wed, Oct 28, 2015 at 2:06 PM, Daniel Jones < daniel.jones(a)engineerbetter.com> wrote: Hi all, Why are logs like those of the CloudController dated by machine-readable timestamps? Are there any tools to parse CF logs in-situ? I find it a constant source of frustration trying to debug an issue reported by a human with a human-parseable date, putting that into a Unix timestamp converter, searching through logs for that timestamp, then scrolling up and down having to occasionally copy/paste a timestamp back into a converter to see if I've gone too far away from my rough target time. Computers are rather good at converting data formats - my brain, not so much. Wouldn't it make more sense to have the logs human-readable by default, and if an automated system needs to ingest those logs, let it do the parsing? Regards, Daniel Jones EngineerBetter.com attachment.html
More All Messages By This Member

1 - 3 of 3

1

Previous Topic Next Topic

Home Hashtags Subgroups Terms