Alternatives
Products that do what STORM Mainframe Resolver Enterprise does
AI-first incident radar for noisy mainframe logs
- 1
- 2
- 3
- 4
- 5
- 6IB
Sup HN, So I got tired of bouncing between Flightradar, MarineTraffic, and Twitter every time something kicked off globally, so I wrote a dashboard to aggregate it all locally. It’s called Shadowbroker. I’ll admit I leaned way too hard into the "movie hacker" aesthetic for the UI, but the actual pipeline underneath is real. It pulls commercial/military ADS-B, the AIS WebSocket stream (about 25,000+ ships), N2YO satellite telemetry, and GDELT conflict data into a single MapLibre instance. Getting this to run without melting my browser was the hardest part. I'm running this on a laptop…
Mar 2026 · github.com
- 7SO
ServiceRadar is an open-source platform for distributed, secure network management and observability, scaling to 100k+ devices. Born from frustration with complex traditional NMS tools like Zabbix, it bridges legacy (SNMP/syslog) and modern (gNMI, OTLP) protocols for cloud-native environments. We built ServiceRadar to simplify monitoring hybrid telecom networks, evolving it into a Kubernetes-native solution with Helm and Docker support. It uses mTLS with SPIFFE/SPIRE, NATS JetStream for event streaming (90M+ EPS), and SRQL for intuitive queries. Integrated with OpenTelemetry,…
Oct 2025 · github.com
- 8
- 9
- 10OO
Hey HN! We’re Max and Thibault building OpenStatus.dev an OpenSource synthetic monitoring platform with incident managements 1 min demo: https://twitter.com/mxkaske/status/1685666982786404352 We have just reached 2000 stars on GitHub https://github.com/openstatusHQ/openstatus We are really excited to hear your feedback/questions and connect further: our emails are [email protected] and [email protected]. Thank you!
2023 · openstatus.dev
- 11
- 12
- 13
- 14NT
nightwatch is a local-first, read-only layer on top of your monitoring. it groups alert storm into incidents, flags noisy checks and has an agent that can investigate for you live systems. You can e.g. jump from the incident into the agent directly. the reason for this weekend project is that we had a kubernetes upgrade that went wrong, and at some point a rollback wasn't possible anymore, so it had to be fixed live during the night while several problems came together. We run a lot of different systems, on-prem and several Kubernetes clusters, and in a situation like that you spend most of…
Jun 2026
- 15BS
Mar 2026 · github.com
- 16SY
Hey HN, we’re Nico and Arseniy, co-founders of Superlog (https://superlog.sh). We're building a self-installing, self healing observability tool meant not to be opened. It has a wizard that daily sets up proper logging and an agent that investigates errors and opens PRs. Super short demo: https://www.youtube.com/watch?v=xFhU9Mk247M. In our earlier startups, we tried Sentry, Datadog, Grafana, Dash0, and nothing was good enough. Proper telemetry and alerting still requires a ton of manual setup. We struggled with adding good logs, so debugging was tough, especially as…
May 2026 · superlog.sh
- 17
XSDR is a unified pipeline for monitoring activity on X and the web. I built it because I wanted my agent to do things based on real-time events that were taking place instead of polling the web or scheduling cron jobs. With XSDR, you can trigger agentic loops based on real-time events. All you need is an API key, a webhook that can receive POST requests, and an idea of what you’re looking for. It currently supports X and Firehose (aka a persistent web crawler).
Jun 2026 · xsdr.app
- 18
- 19LO
Hi HN, I'm Robel. I built LogClaw because I was tired of paying for Datadog and still waking up to pages that said "something is wrong" with no context. LogClaw is an open-source log intelligence platform that runs on Kubernetes. It ingests logs via OpenTelemetry and detects anomalies using signal-based composite scoring — not simple threshold alerting. The system extracts 8 failure-type signals (OOM, crashes, resource exhaustion, dependency failures, DB deadlocks, timeouts, connection errors, auth failures), combines them with statistical z-score analysis, blast radius, error velocity, and…
Mar 2026 · logclaw.ai
- 20LE
I started using Claude Code (claude --dangerously-skip-permissions) and Codex (codex --yolo) and realized I had no reliable way to know what they actually did. The agent's own output tells you a story, but it's the agent's story. logira records exec, file, and network events at the OS level via eBPF, scoped per run. Events are saved locally in JSONL and SQLite. It ships with default detection rules for credential access, persistence changes, suspicious exec patterns, and more. Observe-only – it never blocks. https://github.com/melonattacker/logira
Mar 2026 · github.com
- 21
- 22SY
Hey HN! We’re Abejith and Dev, and we’re building Steadwing (https://www.steadwing.com) - an autonomous on-call engineer that diagnoses production incidents/alerts, correlates evidence across your stack, and resolves them. You can try it at https://app.steadwing.com/signup (no credit card required and a demo mode is available). Every on-call engineer knows the pain. It’s 2am, PagerDuty fires, you open the laptop and start the scramble - Datadog for metrics, GitHub for recent commits, Slack to see who’s awake, Elasticsearch for logs. 45 minutes later you find it…
Mar 2026 · steadwing.com
- 23
Hi HN, I'm Kaushik, and I built Rocketgraph. I believe that while other spaces have caught up to the AI wave, the observability space is still lagging behind, using the same tools and dashboards that we use to analyse logs from human-written code. But now the code is written and debugged by AI, so we need to rethink how we do observability where the observer itself is an AI. The problem that I run into is when an alert fires, I have to manually check the Grafana dashboards and write LogQL queries, which is pretty much like greping. But production usually breaks due to a schema mismatch, or a…
Jun 2026 · github.com
- 24IA
Hello HN! My name is Max, and I’m a co-founder at Lynx (https://uselynx.ai). We’re building an AI-powered incident resolution platform to help engineers debug and resolve on-call issues faster. If you’ve ever been paged in the middle of the night and had to spend hours piecing together logs, metrics, and code, we’d love your feedback. * The Problem * On-call hasn’t kept pace with modern engineering. Even with great observability tools, diagnosing incidents is slow because: - Systems are increasingly complex. - Logs, dashboards, and documentation are scattered. - Context often…
2025
Ranked by how close each launch is in meaning, then by votes. Refine with a description →