Launched this week
Superlog is an open-source autonomous observability tool. It installs itself and fixes the bugs it finds. With a single prompt, it instruments your repository with OpenTelemetry and keeps it up-to-date. When something breaks, it groups noisy issues into a single incident and posts one mergeable PR in Slack. Unlike Datadog or Sentry, there's no setup, no alert fatigue, and no manual fixing. Your telemetry stays vendor-neutral, so you keep full control of your data.
the 'fixes the bugs it finds' claim is the boldest thing in the description and also the one with the most obvious failure modes. an autonomous tool that opens PRs to fix production bugs needs a very clear answer to: what happens when the fix is wrong, who reviews it, what's the blast radius if it gets merged, and how does it know the fix actually solved the problem versus masking it. has anyone shipped this in a production environment and what did the first bad fix look like
Very interesting idea! But for the fixes to be successful, the AI needs to see and remember the entire system and its specific characteristics. When setting it up, do you perform some kind of audit of the whole system and create project-specific rules? What if there is a huge amount of code, including legacy and unused code? Is there any code quality validation before a suggestion is made? What if the proposed change doesn’t work?
superlog
@lakshminath_dondeti Sure thing! Here's our OpenSource repo: https://github.com/superloglabs/superlog
an agent that groups noisy alerts into one incident instead of pinging you 50 times is already worth it. the auto-fix PR on top of that is the part that would've saved our dev team so many 3am debugging sessions
superlog
@tina_chhabra would be happy to take care of it now!!
@tina_chhabra Agree, the PR is the headline, but the judgment layer (does this deserve action at all?), is the real product. That's the decision most tooling still pushes onto humans, and not just in observability
@arseniy_shishaev1 The “which century is it” disorientation at 3 AM is the most accurate description of incident response I’ve ever read. I once spent twenty minutes staring at a dashboard trying to correlate two metrics, only to realize I was looking at staging because my brain hadn’t fully booted yet. The cognitive tax of debugging while half-asleep is real, and it’s rarely accounted for in tooling.
Building monitoring that meets you where your brain actually is at 3 AM, not where it should be, feels like the kind of empathy-driven engineering that prevents burnout as much as it prevents downtime. Congrats on the launch.
superlog
@diana_nadim2 Thank you Diana! Super happy it resonates :) Don't hesitate to give Superlog a try!
superlog
@anusuya_bhuyan exactly!
We were originally Sentry users. Sentry is good, but it tends to overload us with issues without really linking related ones together, which meant we didn't address the real ones as they got lost in the noise. That's why we started using Superlog. Their functionality of grouping issues into actual incidents is great.
superlog
@kabalan_gaspard Thank you Kabalan, appreciate the kind words!