Автоматизация расследований инцидентов

Show HN: DataZen – a local-first client for cross-database workflows My company stopped allowing Navicat because of compliance policy. DBeaver worked, but I don't like it. I kept running into two recurring issues. First, production investigations often require several queries across different databases. I would query one table, copy an ID into another query, wait for the result, and repeat the process several times. I started wondering if there was a way to handle this without writing a separate script for every case. What if I had a simple form where I could enter the query parameters I already knew, and then run a sequence of SQL statements? Following that line of thought, I ended up building Workflow. Superset is a great tool, but as a developer who mostly needed to put together a few r…

Hey folks, I need some guidance here. I spent the last two weeks not coding, but talking to my ICP. I stayed mostly on LinkedIn because I had a 0% reply rate with cold email. So far, I’ve had a few discussions with people working in technical customer support. The goal was to validate the problem, and the problem seems real: people are spending a significant amount of time on investigations, and job postings for technical support engineers clearly state that investigation is part of the role. Quick context on what i am building so you can have the full picture *the product help support and engineering teams investigate complex technical tickets faster.* *It connects to the tools they already use and observability stack to gather customer context, its auto triage and automate the …