[untitled]
28 comments
I love the simplicity, but I would be hesitant to try it since I don’t know what 10MB of logs looks like. I would be interested in trying this if it could be set to auto-evicting past 10MB so I could start to understand that boundary better.
Super interesting! Congrats on the launch.
The use of parquet files and S3 as the main data storage seems interesting, but can you elaborate on how telemetry is optimized for frequent data inserts, since S3 only allows replacing a full file and data cannot be appended directly to it?
Does it mean you use some sort of partitions with many files under the hood or a local buffer (memory/file/db) to make batch updates every x seconds on S3 for better performance?
Would be happy to give it a try!
The use of parquet files and S3 as the main data storage seems interesting, but can you elaborate on how telemetry is optimized for frequent data inserts, since S3 only allows replacing a full file and data cannot be appended directly to it?
Does it mean you use some sort of partitions with many files under the hood or a local buffer (memory/file/db) to make batch updates every x seconds on S3 for better performance?
Would be happy to give it a try!
This is a really nice dev-friendly API, could see it becoming a compelling go-to for eg indie hackers who have moved simple view analytics to reasonably priced tools like Plausible/SimpleAnalytics over the years.
In some ways it feels like Loggly, worth taking a look at their query/dashboard system as it has some really nice tools for clicking around to slice and dice graphs using unstructured data.
Will have to give it a try some time!
In some ways it feels like Loggly, worth taking a look at their query/dashboard system as it has some really nice tools for clicking around to slice and dice graphs using unstructured data.
Will have to give it a try some time!
Awesome product. congrats. I'm curious, can you share more about the security measures in place to protect the telemetry data stored in S3?
thebuilderjr(1)
I'm not quite sure how to place this. For general app telemetry there's https://opentelemetry.io and for tracking user behavior similar to how it's explained in your docs it looks like https://segment.io would be the closest competitor.
How is telemetry.sh different from the above-mentioned?
How is telemetry.sh different from the above-mentioned?
thebuilderjr(1)
Screenshot !
i'm lazy and i don't even test or register/login without screenshot.
i'm lazy and i don't even test or register/login without screenshot.
thebuilderjr(1)