3 Comments

Hi BiteCode, interesting insights as always

I'm asking myself how can I instrument my next project, there are many options here and I am confused. Sentry with his APM features? Posthog? Prometheus to have nice charts on how many times X requests were successfully called or failed? and now Logfire. I'm a bit lost with all that options. Any idea on a simple stack to start with? ^^

Expand full comment
author

Observability is not simple, there are no simple stacks for it, that's why there are so many services that sell it: they sell the convenience.

I do have good things to say about sentry, just the error reporting makes it worth it. I tried manually integrate Open Telemetry with Splunk, and the experience sucked.

All in all, even logging is not great on python, as the api of the logging module has terrible ergonomics and is counter intuitive.

So no, I don't have a great master plan for this. That's why I'm going to give a try to logfire, hoping I may have a turn key solution. Open sourcing is on the road map, and I would love having a self hosting alternative for my personnal projects.

Expand full comment
May 5·edited May 5Liked by Bite Code!

Thank you for the honest answer. I already used Sentry in a previous job and it is really cool!

I agree for the logging part, this is why these days I use structlog in my personal projects. It helps me think of logs as events and not prose.

I will probably used Sentry again and try LogFire, hopefully I will not even need Sentry and it will be the "final" observability solution? Time will tell ^^

Expand full comment