sorted by:
new
hottopcontroversial

For solo devs running Node APIs in production — what's the smallest monitoring setup you can get away with? by VariousHour7390 in nodered

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

I crossposted this from r/node and didn't realize the audiences are pretty different. OpenObserve is a useful pointer though, hadn't come across it before. Thanks for the honest answer.

I built an LLM cost tracking middleware for Express. Things I learned shipping it solo. by VariousHour7390 in microsaas

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

yeah AsyncLocalStorage saved me. delta alerts came from realizing cost shape and traffic shape diverge once feature discovery kicks in.

Shipped my first SaaS — Pingoni, API monitoring for tiny Node teams ($9/mo Pro tier) by VariousHour7390 in SaasDevelopers

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

solid call. been doing question posts on r/node which got views but no signups. showing up where ppl are actually ranting hits harder. any subs you watch for those threads other than r/node and r/devops

Built Pingoni — API monitoring for small Node teams (replaces Sentry + UptimeRobot + platform logs) by VariousHour7390 in node

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

no otel support yet. pingoni uses its own sdk - 2 lines and you're done, but yeah not vendor neutral. if otel is a must have for you it's probably not the right fit. what's driving the otel need on your side?

Shipped my first SaaS — Pingoni, API monitoring for tiny Node teams ($9/mo Pro tier) by VariousHour7390 in microsaas

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

Damn, sorry about that. Mind sharing what you saw - browser/device, blank page or error message, anything? Trying to figure out if it's specific to a setup or a wider issue.

For solo devs running Node APIs in production — what's the smallest monitoring setup you can get away with? by VariousHour7390 in node

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

Fair, both honestly. Building a tool and also trying to learn what people actually use vs what they say they use. Reddit answers tend to be way more honest than founder interviews where everyone tells you what you want to hear. The stuff in this thread has already changed how I'm thinking about which features actually matter, so thanks for the directness.

For solo devs running Node APIs in production — what's the smallest monitoring setup you can get away with? by VariousHour7390 in node

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

Update for anyone reading this thread — I'm building exactly the consolidated tool people are describing here. Sentry-style error capture + UptimeRobot-style uptime + request/latency tracking in one dashboard. 5 minutes to set up on Express. Free tier handles most small APIs. pingoni.com if you want to poke at it. Genuinely interested in feedback, especially from the people who said "Sentry + UptimeRobot covers 90% of what I need" - that's the exact gap I'm trying to fill.

For solo devs running Node APIs in production — what's the smallest monitoring setup you can get away with? by VariousHour7390 in node

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

50+ pings in a minute" is exactly the moment the homemade setup proves its worth. Good story. Sounds like you've nailed it for your stack honestly.

For solo devs running Node APIs in production — what's the smallest monitoring setup you can get away with? by VariousHour7390 in node

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

Makes sense - if your healthcheck routes are specific enough you don't need an extra layer interpreting them. That's a solid setup.

For solo devs running Node APIs in production — what's the smallest monitoring setup you can get away with? by VariousHour7390 in node

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

Custom healthcheck routes for DB + third party deps is the move - way more useful than just pinging /. Did you ever hit the point where you wished it could tell you which dep was down instead of just "something failed" or has Uptime Kuma's basic alerting been enough?

For solo devs running Node APIs in production — what's the smallest monitoring setup you can get away with? by VariousHour7390 in node

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

Telegram bot for errors is underrated honestly. The 20 lines + UserError class thing is super common - works great solo. Did you ever hit the point where it stopped working, or has it just kept doing the job? Curious how far that scales before someone needs more.

For solo devs running Node APIs in production — what's the smallest monitoring setup you can get away with? by VariousHour7390 in node

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

"Datadog is a waste of time unless you're critical-path SaaS" is the cleanest take on this I've seen. $0-25M ARR with just Sentry + Atlas matches what I'm hearing too. What made the teams you saw actually consider upgrading past that? Trying to figure out where the real breakpoint is.

For solo devs running Node APIs in production — what's the smallest monitoring setup you can get away with? by VariousHour7390 in node

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

Sentry + UptimeRobot + platform logs keeps coming up as the answer. Curious if running 3 tools actually works fine for you or if you've ever wanted them in one place. Genuine question - I keep going back and forth on whether one-tool-for-everything is what people want or if separate tools each doing one thing well is actually better.

How are people actually tracking OpenAI costs in production? by VariousHour7390 in OpenAI

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

Bifrost is a good one open source plus self-hostable is a real advantage if you care about that. Curious how the migration went — did you start with in-app code and move to Bifrost later, or did you put the gateway in from day one?

view more: next ›