Not to say that text wasn't structured before, but the format differed for each runtime/logger/platform.

While we discuss the benefits on our timber site, I think a history of logging and an overview of the industry trends would be helpful. There are other companies/people in the space that have come to the same conclusion. If structured logging wins, we win.

A changelog post announcing the new SQL query feature:

• Link to the associated documentation
• Link to a more in-depth blog post

A more in-depth blog post talking about our SQL querying feature:

• How it works (stores data on S3, uses athena, etc)
• Designed for performance (ORC formatted files, partitioned, etc)
• Structured data is automatically available
• Uses presto / athena and all functions available
• Interesting examples (slowest SQL queries and their associated request paths)

Outline

Purpose of this blog post is to show readers how to build a basic state tracking system in a highly distributed and concurrent system in Elixir/OTP.

• Explain the problem we are facing of tracking how many bytes an application has sent in a distributed environment.
• Explain our solution in high with maybe a diagram, this means explaining our usage of GenServer.
• Give a simple example of the usage of GenServer, Registry, and Supervisor.
• Conclude in how this helps track and how it impacts concurrency.