Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Superlog (YC P26) – Observability that installs itself and fixes bugs

superlog.sh

Post reply on HN
Print view View original

21–30 of 60 posts

Re: Show HN: Superlog (YC P26) – Observability that installs itself and fixes bugs

#21

Post by PhunkyPhil »

TZubiri wrote: post #17

Sorry to be crude, but this sounds either dead on arrival, or at least needing a pivot, or a rephrasing of the pitch: The moment something changes the system, it no longer observes it, in fact observing something might cause it to change ( https://en.wikipedia.org/wiki/Observer_effect_(physics) ) Either it's a tool for observing or it's a tool for fixing issues, it cannot be both, by physical principle. Best case sce…

How does a grep or read affect the observing system?

I guess the change in voltages, arrangement of registers, filling of buffers in the network stack are changing but... what?

Re: Show HN: Superlog (YC P26) – Observability that installs itself and fixes bugs

#23

Post by signalbright »

evil-olive wrote: post #19

on your pricing page: > Start with one repo. Price the rest when the signal is real. which makes it sound like possibly the $150/mo price is per-repo? I think that could use some clarification - if I have 10 services in a monorepo vs 10 individual service repos, does that 10x my cost?

Very good point, thank you! Let me remove this phrase, you're right, it's misleading.

The pricing is only by usage (traces/logs/metrics) and investigation credits. We don't charge extra for repos :)

Re: Show HN: Superlog (YC P26) – Observability that installs itself and fixes bugs

#25

Post by signalbright »

sskates wrote: post #20

I love the launch! Automated observability that feeds back into the product development process is the future of this category vs having to spend a lot of time configuring and managing the infrastructure yourself. It's something we've thought a lot about at Amplitude. We'd love to talk.

Awesome, let's definitely have a chat! I'll shoot an email via BF :)

Re: Show HN: Superlog (YC P26) – Observability that installs itself and fixes bugs

#26

Post by signalbright »

OsrsNeedsf2P wrote: post #4

There's very few startups that I look at these days and don't think to myself, "I could just write a Claude skill for that". This one seems pretty cool. Congrats on launch

Thank you! super happy that's how you feel about Superlog. Let us know if you want to try it out and/or have any feedback :)

Re: Show HN: Superlog (YC P26) – Observability that installs itself and fixes bugs

#27

Post by signalbright »

Ember_Wipe wrote: post #18

[flagged]

Very good point on the confidence gate! We've rolled out feedback collection features on PRs themselves, on Slack notifications and incidents a few days ago so the data is still a bit fresh.

Anecdotally, our top clients accept 80-90% of PRs, with several clients accepting all of them and requesting an auto-merge feature. I myself accept most of Superlog PRs to Superlog. Most PRs that stay unmerged are usually due to a client losing interest in our product / abandoning the instrumented project.

Another interesting point is that not every defect is a PR. Often it's misconfiguration in an external service, so there's a special incident state for that. For example, yesterday I forgot to verify our domain on Resend so some verification emails didn't go through. Superlog pinged me on Slack and explained where to go to fix.

Super glad you like the npx onboarding and the MCP tool :) Please keep the feedback coming!

Re: Show HN: Superlog (YC P26) – Observability that installs itself and fixes bugs

#28

Post by signalbright »

aloknnikhil wrote: post #22

The typical issues I have seen with LLMs / Agents tend to be reactive in their fixes. So they tend to "patch" the symptom more than "fix" the root cause. Interested to see how you solve this problem.

You're right! It's a big issue and I don't think there's a silver bullet.

We have an eval suite with code+telemetry fixtures and a golden RCA+patches and an LLM-as-a-Judge. So whenever we get feedback from our users and they're OK with it, we use their feedback to create an eval case (it's still quite manual since you have to calibrate the case).

We use Superlog to observe Superlog, so I often extract cases from our own errors. The PRs get better and better, but, of course, it's sort of a continuous improvement process.

Re: Show HN: Superlog (YC P26) – Observability that installs itself and fixes bugs

#29

Post by tuo-lei »

investigation is the hard part, not generating patches. we've had prod issues where the fix was obvious once you knew the cause, but finding the cause meant connecting an error trace to a config change from 3 deploys ago. if the MCP only surfaces traces and logs from one service the agent is going to propose workarounds instead of actual fixes. how deep does the investigation context actually go?
Post reply on HN