Most of the time, we won't be able to control all of the microservices that we use. Some of them will use one logging library, while others would use a different one. On top of that, the formats will be entirely different and so will their rotation policies. To make things worse, there are still operating system events that we want to correlate with application events. This is where the unified logging layer comes into play.
One of the unified logging layer’s purposes is to collect logs from different sources. Such unified logging layer tools provide many integrations and understand different logging formats and transports (such as file, HTTP, and TCP).
The unified logging layer is also capable of filtering the logs. We may want filtering to satisfy compliance, anonymize the personal details of our customers, or protect the implementation details of our services.
To make it easier to query the logs at a later time, the unified logging layer can also perform...
