No comments yet.
[Why] It all started when I was employed in a full-time job. I got a customer support request for a benign issue. Since I did not want to open my personal laptop at my workspace, I got in the toilet with my laptop bag and fixed the issue.
After a while, I thought about why was I wasting my time with these issues. Was there a better solution?
After trying several different solutions, I threw in the spanner and built my own tool. Behold, Ops!
[Differentiators] Ops is not comparable to a low level logging tool(like greylog).
Its meant for more higher level logging - like user signups, did that cronjob run, received stripe webhook, etc.
These are our differentiators
- Big focus on accessibility and UI. Everyone should be able to view events on their mobile - Actions buttons on events. Use them to trigger webhooks on your server. - Structured events. Pass json, image urls, etc and Ops will render them beautifully - Contextual events. View events within events. Great for understanding complex workflows such as billing webhooks(webhook received -> billing processed -> email sent -> db updated)
[Closing] Right now Ops is closed sourced, but work is underway to building an open source version.
Let me know how you like it!
