On: How to buck a tree: Cutting logs for maximum yield...

[dang]

Submitted title was "Getting the most from your logs".

Since most of the replies were about that, I'm going to move them underneath this stub.

Please use the original title, unless it is misleading or oh never mind.

[dsimmons → dang]

Am I the only one that (wrongly) assumed this was in reference to application logs and not... literal logs? xD

[dopidopHN → dsimmons]

I kept scrolling to see what type of software logs that article was about.

While scrolling I was thinking it was the most well researched and involved tongue in cheek intro I read in a while.

[brudgers → dopidopHN]

  “type of software logs”

  Showing results for *softwood logs*

[m_antis89 → dsimmons]

yes

[LewisVerstappen → dang]

Very good advice. Great tips on logging when you're working with trees.

[brudgers → dang]

Are you saying the title was a clear cut violation?

[manibatra → dang]

The one time I decided to open the link first rather than read the comments.

[AbraKdabra → dang]

I don't know if you deserve a prize or a ban from HN for using that title.

[dvtrn → dang]

Oh for crying out loud

Thanks for the evening chuckle brudgers

[TuringNYC → dang]

I kept thinking this was going to be an Allegory for system logs until I realized it was literal

[joshxyz → dang]

come on. hahahaha.

[hlieberman → dang]

I feel like I just got rick-rolled. I love it; brudgers, you are a mad genius.

[hamasho → hlieberman]

I'm redesigning my project's architecture and like "Wow! This article is so timely!" It's exactly what I felt too.

[physicsgraph → dang]

The best part of this was getting to the tab I had opened long ago and wondering, "how did I get to this page?" and then realizing (after reading it) that I was rick-rolled by HN.

[helsontaveras18 → dang]

Haha love it. Question regarding getting the most from your application logs. My practice is to prefix log statements with the file name and function that’s generating the log. Jumping to that code is just a quick search away. But it does require a bit of manual work to write that extra metadata. I do this because devs just put random logs and it’s so hard to know where they’re coming from. Any best practices?

[jdadj → helsontaveras18]

Not sure about best practices. But at our small shop, we’ve rigged up our homegrown logging infrastructure to do that automatically by using the C/C++ macros __FILE__, __FUNCTION__ and __LINE__

We hide the data in our log viewer to reduce clutter but display it as a tooltip.

[MarkSweep → helsontaveras18]

Various languages have ways of automatically including file paths and line numbers without the caller having to include them every time

C# has CallerFilePathAttribute https://docs.microsoft.com/en-us/dotnet/api/system.runtime.c...

C has the __FILE__, __func__, and __LINE__ pre-processor macros.

[dmckeon → helsontaveras18]

Recently overhauled my rsyslog setup to do timestamps in rfc3339 format. Almost as good as keeping a chain saw chain nicely sharpened, and not replaced backwards!

[mandeepj → dang]

The title can be edited to include “Tree” before “Logs”

[whitesilhouette → mandeepj]

Nah! This one's better. A mood uplift.

[mandeepj → whitesilhouette]

Alright! Perfect example of a little thing bringing happiness for some :-)

[fnordpiglet → dang]

Really I prefer structured logs.

[brudgers → fnordpiglet]

Something like a log cabin maybe?