32 Matching Annotations
  1. Last 7 days
  2. Nov 2022
  3. Oct 2022
  4. Aug 2022
    1. Process the log file to determine the spread of data: cat /tmp/sslparams.log | cut -d ' ' -f 2,2 | sort | uniq -c | sort -rn | perl -ane 'printf "%30s %s\n", $F[1], "="x$F[0];'
  5. Apr 2022
  6. Mar 2022
    1. In any significant project I worked in the last 15 years, logging text messages resulted in a large amount of strings which was hard to make sense of, thus mostly ignored.

      hard to make sense of, thus mostly ignored

  7. Jul 2021
  8. Apr 2021
    1. Lumberjack 1.0 had a concept of a unit of work id that could be used to tie log messages together. This has been replaced by tags. There is still an implementation of Lumberjack.unit_of_work, but it is just a wrapper on the tag implementation.
  9. Mar 2021
    1. Pluggability uses the Loggability library. Just set the log level to 'debug' and it'll explain what's going on:
  10. Jul 2020
  11. Apr 2020
  12. Feb 2020
  13. Oct 2018
  14. Jun 2018
  15. Apr 2018
    1. Format clock summary as x:xx

      Dont do this I hate invisible zeros

    2. Log the time a task is completed.

      used to (setq org-log-done-with-time t)

  16. Jun 2017
    1. incidents are an unavoidable reality of working with distributed systems, no matter how reliable. A prompt alerting solution should be an integral part of the design,

      see how it can hook into the current logging mechanism