Logging Concepts

TreeScale Platform keeps logs for every request to the target TreeScale App. It is designed to help with app debugging for production and set triggers on unwanted results later.

The logging process happens independently from an actual request, which is proven that does not affect the request/response performance. We use an application proxy like Nginx, which has specific logging principles to ensure we are not affecting TreeScale App performance by logging request/response cycles.

It is important to note that we are removing all application logs and information attached to them right after the TreeScale App gets removed from our platform. So there is no information leftovers, even for the application logs.

App Logging

By default, in the TreeScale Debugger UI, we are not keeping logs, just because usually the application debugger interface is used to make quick checks without extra references for the future. However, when you do REST API calls using the production URL like https://app1.tsapp.dev we keep all request/response logs when they have passed the valid authentication process.

The critical part to remember is that we are keeping request logs only for valid requests, which means if you send an invalid request with the wrong parameters or Authentication header, you will get back an error status code. Still, we would not save the request log.

Query Historical Logs

You will get only three days of logging history for the free package plan. However, you can query logs and set specific triggers for the paid plans to identify application prompt failures or potential security issues.