Logging as a service. It's a very simple logging service that saves only logs and gives an ability to scan them. The service is following DomainDrivenDesign, CQRS, Repository patterns. It looks like overengineering, but I do believe that a project will grow and these things will be necessary.
docker image: docker pull diyaz/service-log:latest
For inspecting logs use Web UI, there is also searching form. Logs can be saved in several ways:
Certain workers (scrapers, consoles, whatever applications) can save logs directly to DB via sl.infrastructure assembly. The assembly has necessary validation logic to protect from invalid data.
Certain workers (scrapers, consoles, whatever applications) can send logs to the WebApi endpoint. There is a Swagger Api documentation, where models and methods are well described.
List of logs:
Viewing a particular log:
Let's take an unhandled error as an example. Usually, when something goes wrong, application should notify a user about it. After that, the user see a message like "Something goes wrong!", then the user wants to understand what it was and, of course, avoid this kind of error in the future. Unfortunately, when people inform tech support about some bad behavior, most of them can't describe properly a problem and what they did. So consequently, the support gleans information from million logs and subjective client's description. It's not a fast and good way of solving the problem. However, what if a user can provide a link with the log that contains all the information: when? how? where? and stack trace :).
service-log is MIT licensed.