SmartLogger

Dashboard - List of channels
Dashboard - List of recent logs in every channel
Channel Statistics
Log meta data

Problem

When you are the company owner/manager/decision maker, you have to fix the most critical bugs first. On a large project, when there are hundreds of bugs, it becomes harder to keep track of just how much money company loses because of bugs.

Solution

With a simple bug-reporting setup SmartLogger will collect, analyze the bugs and calculate how important is it to fix the given bug based on the amount of revenue company potentially loses because of it.

At the end of the day, you will have a clear overview of potentially most expensive bugs & bottlenecks in your application.

Why SmartLogger

There are a TON of other log collecting services available on the market (Loggy, Zettalogs, Splunk etc). They all store, analyze and give insights about bugs in your applications. The difference with us is that we use the log data to determine exactly where the company is losing money and we help you to prioritize what to fix first.

Challenges we ran into

The main challenge was to make sure the service is able to handle large traffic. With a set of caching practices and Redis SmartLogger is able to scale up easily.

Business Side

SmartLogger will be a paid service. There will be multiple membership plans with different limits of Traffic and number of Channels. Similar to other log collecting SaaS platforms.

Technical Details

Developer(s) working on company's app, can define the bug categories, let's call them channels. They stream the logs on the channels.
Each of the log entry must contain the MS (MonetaryScore) attribute which defines how much damage company takes when this bug occurs (This is of course arbitrary value).
SmartLogger keeps track of bugs and their MS's to calculate the total damage of bug received on a particular Channel.
SmartLogger uses the data generated above to show insightful information about the processes that cost company the most amount of money.

The beauty of our solution is that it's very flexible - It can estimate the amount of damage taken starting from simple error 404 pages to much more complex UX issues.