If you’ve ever been enraptured by the magical world of gaming, you’ve likely encountered Blizzard Entertainment. Known for its high-octane, immersive games, Blizzard has long been a beacon of quality in the gaming universe. Their latest offering, Diablo 4, has taken the gaming community by storm, breaking records and setting new standards for commercially and technically successful game launches.
Unless you live under an actual rock and haven’t hauled yourself into modern times, I’m sure you know – and most likely use – JavaScript. You know, the versatile and dynamic programming language that powers the web and beyond. From client-side scripting to server-side computing, and even robotics, JavaScript is everywhere. However, like any good craftsperson, a JavaScript developer knows that their work is only done once it’s been tested.
A paradigm shift is overdue in the realm of software observability. While Site Reliability Engineers (SREs) have been having fun with metrics, traces, and logs, software developers have been left in the lurch, shackled to the conventional, low-fidelity tool of logs. Why should SREs have all the fun, right? Welcome to the dawn of a new era. An era where developers, too, can enjoy superior observability engineering. That’s where the fourth pillar of observability comes in: Snapshots.
Logging is ancient history. You know – old and outdated. At one time, it was the best method – like sending carrier pigeons to convey messages – but we live in an ever-changing world. Long gone are the days in which logging was the primary method when troubleshooting and debugging. Any developer who was written millions of log lines can attest to the fact that they’ve probably needed to access maybe 1% of those.
Cloud logging services have long been plagued by limitations and high costs, hindering companies’ ability to achieve true flexibility in their operations. One of the primary obstacles is the lack of flexibility in traditional cloud logging services, which often require companies to make upfront decisions about log levels and storage capacity, locking them into fixed plans for extended periods.
