Show HN: HyperDX – open-source dev-friendly Datadog alternative
First paragraph <a href="https:&#x2F;&#x2F;github.com&#x2F;hyperdxio&#x2F;hyperdx">https:&#x2F;&#x2F;github.com&#x2F;hyperdxio&#x2F;hyperdx</a><p><i>&quot;HyperDX helps engineers figure out why production is broken faster by centralizing and correlating logs, metrics, traces, exceptions and session replays in one place. An open source and developer-friendly alternative to Datadog and New Relic.&quot;</i><p>Just perfect. Bravo.<p>--<p>As a merc, I never understood the why of Datadog (or equiv). The teams and projects I rotated thru each embraced the &quot;LOG ALL THE THINGS!&quot; strategy. No guiding purpose, no esthetics. General agreement about need to improve signal to noise ratio. But little courage or gumption to act. And any such efforts would be easily rebuffed by citing the parable of Chesterfordstorm&#x27;s Fences of Doom and something something about velocity.<p>Late last century, IT projects, like CRMs and ERPs, were plagued by over collection of data. Opaque provenance, dubious (data) quality, unclear ownership, subtractive value propositions (where the whole is worth less than the parts). No, no, don&#x27;t remove that field. We might need it some day.<p>Today&#x27;s &quot;analytics&quot; projects are the same, right? Every drive-by stakeholder tosses in a few tags, some misc fields, a little extra meta. And before anyone can say &quot;kanban&quot;, the stone soup accreted enough mass to become a gravity well threatening implosion dragging the entire org-chart into the gapping maw of our universe&#x27;s newest black hole.<p>Am I wrong?<p>But logging is useful, right? Or at least has that potential.<p>The last time I designed a system end-to-end, that&#x27;s kinda what we did. Listed all the kinds of things we wanted to log. Sorta settled on formats and content (never really ever done). Did regular log bashs to explain and clear anomalies. Scripts for grooming and archiving. (For one team I rotated thru, most of their spend was on just cloudwatch. Hysterical.)<p>But my stuff wasn&#x27;t B2C, so wasn&#x27;t tainted by the attention economy, manufactured outrage, or recommenders. No tags, referrers, campaigns, etc. It was just about keeping the system up and true. And resolving customer support incidents asap.<p>Does any one talk or write about this? (Those SRE themed novels are now buried deep in my to read pile.)<p>I&#x27;d like some cookbooks or blue prints which show some idealized logging strategies, with depictions of common enough troubleshooting scenarios.<p>Having something authoritative to cite could reduce my semblance to an Eeyore. &quot;Hey, team mates, you know what&#x27;d be really great?! Correlation IDs! So we can see how an action percolates thru our system!&quot;<p>Just curious.<p>PS- Datadog&#x27;s server hexagon map&#x2F;chart thingie is something else. The kind of innovation that wins prizes.