Logs can be a nightmare sifting through log files to understand what went wrong (when things go wrong). Now we aren't saying that Timebeat is going to go wrong, but it is nice to be able to quickly identify what went wrong, or if something is going to go wrong.
Rarely do engineers just have a look at a log file to see if all is running as expected, but sometimes they can hold important information to stop outages or increase the performance of the application.
So with Timebeat we came up with a solution; why not log the important items (and a few informational items) to the database and give them a dashboard.
Logs, logs, and more logs:
The logs dashboard is broken up into simple easily recognisable items, and the colour coordination makes it that much easier at a glance. The top bar chart is a running count of log items, colour coded for severity (Green= info, Yellow= warn, red= error, purple= critical and blue= debug). This is useful for understanding how often informative logs are being logged, in most cases, this is populated on the start-up of the TImebeat application or when the application stops. Below the bar graph is simple visualisation that represents the various log levels in their respective colour. The left-hand side depicting the count and the right hand visual being the log message itself so you know exactly what is going on with your application.