Building Telemetry Tracker

A few months ago, I started building something I thought only I would use. I started building Telemetry Tracker. Honestly, it wasn't supposed to become a product. I wanted a place where I could experiment with telemetry, SDKs, dashboards, and backend architecture. I was also getting tired of setting up different analytics and monitoring tools for every side project. So I thought... why not build my own?

At first, it was just for me. Then I started using it in more and more projects. Eventually, I realized it had become something worth open-sourcing.

Why another telemetry platform?

I get this question quite a bit. There are already great products like Sentry, PostHog, Datadog, and plenty of others. I'm not trying to replace them. Telemetry Tracker exists because I wanted something that fits the way I like building software.

• Open source
• Self-hostable
• Easy to integrate
• Built with TypeScript from top to bottom

Most importantly, I wanted something I'd actually enjoy maintaining.

What it does today

Today, Telemetry Tracker supports:

• Error tracking
• Product analytics
• Custom events
• Sessions
• Source maps

There are official SDKs for:

• React
• Next.js
• Vue
• Nuxt
• React Native
• Node.js
• NestJS

There's still a long roadmap ahead, but it's already running in several of my own projects every day.

The biggest surprise

I thought building the software would take most of my time. It didn't. Writing the code is actually the fun part. The part I underestimated was everything around it.

• Writing documentation
• Reviewing pull requests
• Keeping GitHub organized
• Writing release notes
• Building the website
• Answering questions

I probably spend almost as much time outside my editor as I do inside it now. Maintaining an open-source project is a completely different skill from building one. I'm still learning that every day.

Open source has been the best part

One of my favorite moments was getting the first pull request from someone I'd never spoken to before. Then another. Someone translated the README into German. Someone else improved the GitHub Action for source map uploads. Those are small contributions, but they make the project feel alive. That's something I never really experienced with private side projects.

What's next?

There's still plenty I want to build. Performance Monitoring is the next big milestone. After that, I want to add alerts, session replay, and continue improving the developer experience. I'm sure a lot will change along the way. That's part of the fun.

If you'd like to check it out, I'd genuinely love to hear what you think. Whether it's feedback, criticism, or feature ideas-I'm all ears.

⭐ GitHub: https://github.com/Telemetry-Tracker/telemetry-tracker
🌐 Website: https://telemetry-tracker.com

Thanks for reading! 👋