Re^5: WWW::Mechanize::Chrome : random complaining that Log4perl is not initialised and test fails

Yes, the configurable options are great.

I think the main thing I'm missing, especially with WWW::Mechanize::Chrome logging, is a good structured log viewer, that lets me fold/unfold log messages and displays JSON (or Dumper output or whatever) in a structured view.

But down that road lies the madness that is Kibana and Elasticsearch.

Comment on Re^5: WWW::Mechanize::Chrome : random complaining that Log4perl is not initialised and test fails

Replies are listed 'Best First'.
Re^6: WWW::Mechanize::Chrome : random complaining that Log4perl is not initialised and test fails by talexb (Chancellor) on Aug 15, 2025 at 14:33 UTC
.. a good structured log viewer, that lets me fold/unfold log messages and displays JSON (or Dumper output or whatever) in a structured view. I suppose you could fold/unfold lines like hiding DEBUG level messages but display everything else, but only keep the full file around for a while. After a day or two, perhaps filter the log file to delete the DEBUG information, and keep the reduced files around a little longer. Every situation is different, though, and it depends on how much space you have for log files, what detail level you want to keep, how far back you want logs for, and whether there's PII in the log files. Alex / talexb / Toronto As of June 2025, Groklaw is back! This site was a really valuable resource in the now ancient fight between SCO and Linux. As it turned out, SCO was all hat and no cattle.Thanks to PJ for all her work, we owe her so much. RIP -- 2003 to 2013.	[reply]

Replies are listed 'Best First'.

Re^6: WWW::Mechanize::Chrome : random complaining that Log4perl is not initialised and test fails
by talexb (Chancellor) on Aug 15, 2025 at 14:33 UTC

.. a good structured log viewer, that lets me fold/unfold log messages and displays JSON (or Dumper output or whatever) in a structured view.

I suppose you could fold/unfold lines like hiding DEBUG level messages but display everything else, but only keep the full file around for a while. After a day or two, perhaps filter the log file to delete the DEBUG information, and keep the reduced files around a little longer.

Every situation is different, though, and it depends on how much space you have for log files, what detail level you want to keep, how far back you want logs for, and whether there's PII in the log files.

Alex / talexb / Toronto

As of June 2025, Groklaw is back! This site was a really valuable resource in the now ancient fight between SCO and Linux. As it turned out, SCO was all hat and no cattle.Thanks to PJ for all her work, we owe her so much. RIP -- 2003 to 2013.

[reply]