JSON

Let's start with a short story (by Treasure Data):

 

Now, just imagine, the "little Web interface" is Logz.io and "Bob" is our support team, who is happy to assist you with all of your parsing needs. But what if you did not have to rely on us whenever changes are made to your logs? And as you know, by adding new features to your application, changes to your log structure may be inevitable.

The solution? Structured logging, start logging as JSON. The idea is simple: instead of parsing your application logs in JSON objects that are indexed into Elasticsearch, you can just log your application as JSON objects directly. The advantage here is that the data will be already structured in a format that Elasticsearch handles.

 

If you are interested in learning more about this, we recommend the following links:

  1. How to Log a Log: Application Logging Best Practices
  2. The 10 Commandments of Logging