6 Comments

"Your team wants to start with a free solution"

Free is never really free. I have found that developers are attracted to open source "free" tools because they like the challenge and are tinkers by nature. We need tinkers. But, it cost in terms of productivity and maintenance over time. Free to download. Free to use. But not free to the project.

Love the write up and sharing of your findings. I look forward to more.

Expand full comment

Total agree. In my experience starting with something that doesn't need budgetary approval helps in selling the paid solution. Curious if others have experienced the same.

Expand full comment

Great article! I think it's a fine balance between money, time, and knowledge. Unfortunately those that have smaller teams are also those with smaller budgets. AND those that need the expensive automated tools the most!

Expand full comment

Great write-up Sarah. Our observation was that the majority of the tools you name are mainly built for relational data. We have been working for a decade with time-series (sensor data /IoT) and in this domain you need time-series specific metrics. And remediation (from unreliable to reliable) is possible here. That's why we started building Timeseer.AI btw...

Expand full comment

Have you found any tools with good "issue resolution" flows? Any open source options there?

Expand full comment

I would think some of the tools in the list integrate with something like Sentry, but that's not open source. It does have great issue resolution though.

Expand full comment