44 Matching Annotations
  1. Jul 2023
    1. Rails' default approach to log everything is great during development, it's terrible when running it in production. It pretty much renders Rails logs useless to me.

      Really? I find it even more annoying in development, where I do most of my log viewing. In production, since I can't as easily just reproduce the request that just happened, I need more detail, not less, so that I have enough clues about how to reproduce and what went wrong.

    2. Lograge is an attempt to bring sanity to Rails' noisy and unusable, unparsable and, in the context of running multiple processes and servers, unreadable default logging output.
  2. Mar 2023
  3. Dec 2022
    1. On the Provider and Logs tab, in the Name column, select Lesson 3 Log File. After you have created a log provider for your package, you can optionally deselect it to turn off logging, without having to delete and re-create a log provider.

      To turn it on and off you need to know to select the checkbox and toggle the checkbox with the spacebar.

    2. On the Details tab, in the Events column, select the PipelineExecutionPlan and PipelineExecutionTrees events.

      No matter where I click in the package tree, ell options in the Details pane are "dimmed" as the note describes.

      There is an alert at the bottom of the window that says: "⚠️ To configure unique logging options for this container, enable logging for it in the tree view."

      EDIT: We discovered that selecting the checkbox and hitting space un-mutes the field, then the checkbox can be toggled with the space bar.

      With it toggled OFF, you can then go to the Details tab and toggle the settings as required, then go back to the Providers and Logs tab and toggle it ON.

    3. In the Containers pane, expand all nodes of the package container hierarchy, and then clear all check boxes, including the Extract Sample Currency Data check box. Now select the check box for Extract Sample Currency Data to get only the events for this node.

      When I completed this step, the nodes of the package container hierarchy did not have checkboxes. Also, the Extract Sample Currency Data checkbox did not respond to my clicks.

      There was a message to clear the parent, but since the parent had no checkbox, I was unable to do so.

      Drilling down resulted in checkboxes that "appear dimmed" as in the note below.

      This appears to be a bug or at least a lapse in the documentation.

      EDIT: We found a work-around. You can highlight the checkbox and tick it with the spacebar - but you can't select it with the mouse.

      On the Lesson 3 root node, under Select the logs to use for the container: I was able to select the checkbox.

      When I navigate deeper though, this option is unchecked and muted or grayed out with a message at the bottom reading:

      "⚠️ To configure unique logging options for this container, enable logging for it in the tree view."

  4. Nov 2022
  5. Oct 2022
  6. 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];'
  7. Apr 2022
  8. 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

  9. Jul 2021
  10. 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.
  11. Mar 2021
    1. Pluggability uses the Loggability library. Just set the log level to 'debug' and it'll explain what's going on:
  12. Jul 2020
  13. Apr 2020
  14. Feb 2020
  15. Oct 2018
  16. Jun 2018
  17. 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)

  18. 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