-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Description
As discussed briefly here #725, async logging can be useful:
As commented above the primary benefit is reducing time taken per transaction/request. It’s not uncommon for a service to log messages for each request to a service. When using synchronous logging the time taken to perform the I/O operations are included in the response time.
If using asynchronous logging applications can reply back to a request while the I/O operations happen in the background.
This is a very common practice in high volume and low latency applications.
My primary question is. Is this something that the maintainers have specifically chosen not to do, or is there appetite but it just hasn’t been contributed yet?
This was discussed 7 years ago. Does the current state of logrus make it capable of structured logging?