Operations | Monitoring | ITSM | DevOps | Cloud

Article updated June 2024 Is your current Subversion (SVN) version control system not meeting the needs of your development team? Perhaps you’ve heard of Git, but you’re so entrenched in SVN that converting to a new version control system seems like a daunting task. Fear not! No task is insurmountable when you have the power of the legendary GitKraken Desktop on your side.

In the ever-evolving landscape of networking, there are a plethora of three-letter acronyms that make up the wonderful alphabet soup that is a part of every engineer’s vocabulary. Whether it’s TCP, UDP, SSH, or one of the many other dozens, one acronym is commonly left out of the discussion: DDI. These seemingly simple letters are often overlooked or rarely thought of, but they are a crucial foundation for managing a stable, secure, and efficient network.

Each year, financial services organizations handle billions of transactions, through which trillions of dollars of commerce flow. Customers expect key services, from online banking and cash transfers to payroll services, to be available around the clock, just as they expect their assets, data, and identities to be kept secure. Meanwhile, financial institutions themselves must be able to maintain ongoing communication with clearing houses, stock markets, payment processors, and other relevant parties.

In the not-too-distant past, building software was relatively straightforward. The simplicity of LAMP stacks, Rails, and other well-defined web frameworks provided a stable foundation. Issues were isolated, systems failed in predictable ways, and engineers had time to innovate on new features for the business. And it was good.

Hello, Mattermost community! I’m Andrew Zigler, a developer advocate here at Mattermost, and I’ve recently had the privilege of representing our open source research at two great cybersecurity community conferences: BSides Barcelona 2024 and AppSec SoCal 2024.

Welcome to the Inside Elastic blog series, where we showcase Elastic's internal operations solving real-world business challenges. This specific series will shed light on our journey to integrate generative AI into our customer success and support operations, providing you with a behind-the-scenes look at our process. We’re blogging about this capability as we’re building it, and we’re excited for you to join the ride!

Redis is no longer open source. In March 2024 the project was relicensed, leaving its vast community confused. But the community did not give up, and started work to fork Redis to keep it open. On my recent OpenObservabilty Talks episode, I delved into Valkey, a prominent fork of Redis.

I'm excited to share that Gartner has included Monitoring as Code (MaC) as an emerging practice to their Hype Cycles for SREs again, the second year in a row. Since we founded Checkly, our vision has been that monitoring should sit in your repository, be codified, and scale with your software development. There is no alternative to MaC as it allows your engineering team(s) to work together, create and maintain checks, and ultimately own their monitoring.

As first announced during Sentry Launch Week, we have been working on shipping a major release of our JavaScript SDKs. This update makes getting started with Sentry JavaScript SDKs (even more) straightforward. This release broadens the number of frameworks and libraries where we provide automatic instrumentation, meaning you can access telemetry data in Sentry on day one, without configuration.

Testing NetFlow used to require time, expertise, and lab equipment. Using Kentik and the new Kappa agent, it can be done in minutes with nothing more than a spare Linux machine.