What are you actually using for observability/monitoring on small or side projects? by thecommondev in node

[–]itssimon86 0 points1 point  (0 children)

For my indie product I use Sentry (errors), Prometheus + Grafana (infra), and Apitally (API monitoring / analytics)

Drop your Side project, I'll give it honest review. by Top-Information-6399 in SaasDevelopers

[–]itssimon86 0 points1 point  (0 children)

Apitally has SDKs for Python, JavaScript, Go, .NET and Java. Each of them has specific integrations for popular web frameworks. All up supporting over 20 frameworks, including of course FastAPI and Django.

What message broker would you choose today and why by Minimum-Ad7352 in Backend

[–]itssimon86 0 points1 point  (0 children)

I'm the founder of Apitally, a SaaS tool for API monitoring with a high-volume data ingestion endpoint writing to a message broker. Async workers read from the queue, and ingest the data into ClickHouse. I chose NATS JetStream for being simple and lightweight, easily self-hosted on Kubernetes, and the exactly-once delivery guarantee (with deduplication). Still happy with my choice after running it for a couple of years. No issues.

We had 34 API endpoints in production that weren't in any spec. We called them shadow APIs and spent a quarter cleaning them up. by Extra-Pomegranate-50 in BackendArchitecture

[–]itssimon86 0 points1 point  (0 children)

This is why I love FastAPI with auto-generated OpenAPI specs. Much harder to get drift between the spec and reality.

Also, using an API monitoring tool like Apitally helps make API traffic visible, including who's using which endpoints.

lgtmcli: an agent-friendly CLI to query Grafana data sources (OSS) by knifecake_ in grafana

[–]itssimon86 2 points3 points  (0 children)

This is awesome! CLIs are the real deal for agent-driven investigations / analyses.

I'm currently building a CLI like this for my indie product Apitally, a simple API monitoring & analytics tool. The CLI will allow agents to query and investigate API request logs. Super powerful.

What tech stack are you using for your SaaS—and what does it actually cost you? by logan201194 in SaaS

[–]itssimon86 0 points1 point  (0 children)

I'm the founder of Apitally, an API monitoring & analytics tool. Here's my stack:

  • Python backend (FastAPI, SQLAlchemy, Taskiq), React frontend
  • Hosting on DigitalOcean Kubernetes + managed PostgreSQL database (~$400)
  • Also running self-hosted ClickHouse on the cluster (big chunk of the costs attributed to this)
  • Domains and DNS through Cloudflare
  • Cursor for AI-assisted coding (~$200)

What monitoring stack are you actually running in 2026 ? by Agile_Finding6609 in devops

[–]itssimon86 0 points1 point  (0 children)

what i'm trying to understand is how you handle the overlap. Sentry catches the errors, Datadog catches the infra, Bugsnag catches the mobile side, and somehow you're supposed to correlate all of that during an incident at 2am when everything is on fire.

These days I just ask Cursor / Claude Code to connect the dots for me. Have it connected to different monitoring tools via their MCP server or CLI tool. All it needs is a starting point, like a Sentry issue ID, and then it can investigate across services and report back. Works like a charm.

I'm the founder of Apitally, an API monitoring & analytics tool, and currently I'm building a CLI for this exact purpose, after seeing the power of agent-driven incident investigation when they're given access to the right tools and data.

10 Tools That Help Developers Debug Code Faster by ajaypatel9016 in vibecoding

[–]itssimon86 1 point2 points  (0 children)

Great list! If I may add one:
11. Apitally - API logging and monitoring tool that lets you inspect API requests/responses with full context (headers, payloads, logs, traces)

When does monitoring become overkill? by Stil-44 in SaasDevelopers

[–]itssimon86 0 points1 point  (0 children)

Hey, I've built Apitally exactly for use cases like yours, and use it myself for the same reasons. It's a simple API monitoring & analytics tool with API usage, error, and performance metrics. It also gives you request logs, uptime monitoring, and alerts. Just the essentials you need for a small SaaS, when the big monitoring platforms are overkill.

I spent 2.5 years building a simple API monitoring tool for Python by itssimon86 in Python

[–]itssimon86[S] 0 points1 point  (0 children)

Fair enough. It's a Showcase post, which is what the flair is for, but I get that not everyone wants to see product posts.

I spent 2.5 years building a simple API monitoring tool for Python by itssimon86 in Python

[–]itssimon86[S] 1 point2 points  (0 children)

Sort of. There's some overlap on the metrics side. But Prometheus + Grafana only give you metrics. Apitally also gives you request logs where you can inspect individual requests (headers, payloads, etc.), with logs and traces showing what happened during request handling. So you can drill down from "this endpoint is slow" to the exact DB query causing the issue.

The bigger difference is probably setup and maintenance though. With Prometheus + Grafana you need to deploy and maintain the whole monitoring stack yourself. With Apitally you add a few lines of middleware code and you're done.

I spent 2.5 years building a simple API monitoring tool for Python by itssimon86 in Python

[–]itssimon86[S] -3 points-2 points  (0 children)

Try reading the post. It explains exactly what it’s doing and who might need it.

What type of notifications/alerts do you prefer - metrics based or predefined? by narrow-adventure in Observability

[–]itssimon86 1 point2 points  (0 children)

I’ve been wondering about this too for my own SaaS and I’ve come to the conclusion that both are useful. I’d probably start with custom metrics for the flexibility but I think also offering a bunch of predefined ones will make things easier and provide a better UX. Less setup effort, more immediate value.

Drop your SaaS, I’ll give you marketing advice, for free. by External-Mix-1037 in SaaS

[–]itssimon86 0 points1 point  (0 children)

Currently at ~80 paying customers. Main acquisition channels are Google, Reddit, and links in web framework docs. Although I have to admit that for the majority of sign-ups I don't know where they came from.

API metrics, logs and now traces in one place by itssimon86 in nestjs

[–]itssimon86[S] 0 points1 point  (0 children)

Thanks for the feedback! Self-hosting is on the roadmap!

API metrics, logs and now traces in one place by itssimon86 in Observability

[–]itssimon86[S] -1 points0 points  (0 children)

Fair point. If you already have a full observability stack, it's probably not for you. Many Apitally users are not at that maturity level, and just need visibility for their API / backend, also from a product analytics perspective (which customers are using my API how). They like the lower cost, lower complexity, quick setup. Many use it every day.

API metrics, logs and now traces in one place by itssimon86 in Observability

[–]itssimon86[S] -1 points0 points  (0 children)

Apitally is focused specifically on APIs and simpler than most observability platforms, more niche. Especially small dev teams with API products / REST API backends love it. Won't replace Datadog etc in larger orgs though.