We are using the Timesheet Reports and Gadgets Add-On for JIRA. It’s available on the Atlassian Marketplace under a BSD licence, but it’s not free. On our JIRA 5.0.x server, it was accessible from the Projects tab > Summary page > Reports drop-down list > Time Sheet Report item. After upgrading to JIRA 6.x, it … Read more
This is a great question! Here’s a first cut. Be able to log at multiple levels (ex: debug, warning, etc.). hslogger is easily the most popular logging framework. Be able to collect and share metrics/statistics about the types of work the program is doing and how long that work is taking. Ideally, the collected metrics … Read more
I usually try to use it like this: DEBUG: Information interesting for Developers, when trying to debug a problem. INFO: Information interesting for Support staff trying to figure out the context of a given error WARN to FATAL: Problems and Errors depending on level of damage.
To expand on ypocat’s answer, since it won’t let me comment: start-stop-daemon –start –quiet –chuid $DAEMONUSER \ –make-pidfile –pidfile $PIDFILE –background \ –startas /bin/bash — -c “exec $DAEMON $DAEMON_ARGS > /var/log/some.log 2>&1” Using exec to run the daemon allows stop to correctly stop the child process instead of just the bash parent. Using –startas instead … Read more
Create a single log.Logger and pass it around? That is possible. A log.Logger can be used concurrently from multiple goroutines. Pass around a pointer to that log.Logger? log.New returns a *Logger which is usually an indication that you should pass the object around as a pointer. Passing it as value would create a copy of … Read more
Understanding dmesg timestamp is pretty simple: it is time in seconds since the kernel started. So, having time of startup (uptime), you can add up the seconds and show them in whatever format you like. Or better, you could use the -T command line option of dmesg and parse the human readable format. From the … Read more
There is a command line option for logging. The output is saved to screenlog.n file, where n is a number of the screen. From man pages of screen: ‘-L’ Tell screen to turn on automatic output logging for the windows.
How about this option: docker logs containername >& logs/myFile.log It will not redirect logs which was asked for in the question, but copy them once to a specific file.
slf4j wrappers Most of Scala’s logging libraries have been some wrappers around a Java logging framework (slf4j, log4j etc), but as of March 2015, the surviving log libraries are all slf4j. These log libraries provide some sort of log object to which you can call info(…), debug(…), etc. I’m not a big fan of slf4j, … Read more
This table might be helpful for you: Going down the first column, you will see how the log works in each level. i.e for WARN, (FATAL, ERROR and WARN) will be visible. For OFF, nothing will be visible.