Quicklog.io

Spend less time reading logs

Visit Website
November 8, 2018 Product Hunt launch

After stressing about this for too long, I just set the listing free. It got a few handfuls of upvotes but made no real impact.

I knew that this was a niche product and was going to take some marketing work, I just had no idea how much that will become.

www.producthunt.com/posts/quicklog-io

Comment

August 6, 2018 Eureka! moment

Ever since using a centrallized log collector (primarily Loggly.com), I've come to realize that I've developed a certain motor memory sequence of actions when navigating logs while analyzing an issue. It dawned on me that this can and must be automated. I can't actually recall the exact date this occurred, but this day of August 6 is when I started to do something about it.

Since I was already playing around with Vue.js as a more pleasent alternative to React, it was only natural that I would build a back-end and APi just so I could try out this new front-end wonder.

This is when QuickVue was created along with its back-end Quicklog. I decided to build the back-end in Go mainly for its runtime efficiency and ease of deployment. Java, Kotlin or Elixir would have been other prime candidates. The decision was made without much tought as it was then just a side project whose purpose was to enable trying out the Vue.js front-end. I haven't regretted this (yet).

github.com/karmakaze/quickvue\
github.com/karmakaze/quicklog\
loggly.com

Comment

About

As a Site Reliabilty/Platorm Engineer, I have spent a substantial amount of time reading and analyzing logs to determine what did happen, what didn't happen, or why. I realized that this can be dramatically improved.