In a 2019 Top Trends Transforming Network Operations survey, 34% of networking pros identified improving network agility as their top business goal for the year. The stat isn’t surprising. “Network agility” is considered the future of networking, but the term itself has become a bit of a buzzword. Everyone’s talking about it, but no one can agree on its definition. So what does network agility actually mean? We surfed the web and analyzed what (almost) everyone has to say.

Kubernetes is great but complex! Whether to enable hybrid and multi-cloud, promote deeper specialization among development teams, enhance reliability, or simply stay ahead of the curve, organizations are reaping the varied benefits of this technology investment— but it comes at a cost. With each optimization, there are tradeoffs. With each layer of abstraction comes less visibility, resulting in more complexity when something goes wrong.

By Des Nnochiri Budgetary constraints are often a key factor in determining how an organization sets up its IT infrastructure. The hybrid cloud typically leads to cost savings of between 5% and 30% for enterprises that make the transition. Besides the monetary aspects, performance benefits and easier administration also inspire many organizations to consider moving to a hybrid cloud.

Earlier this month we announced the latest iteration of our award-winning hybrid IT infrastructure management and AIOps platform, VirtualWisdom. This was one of our biggest product-related announcements of the year, and we were thrilled with the response we received not only from our partners and customers, but also from the media and analyst community. Let’s take a look at what some folks had to say about the new VirtualWisdom.

One of the most common reasons for system failures is changes to the underlying infrastructure. Amazon CloudTrail does a great job of recording when actions are taken but a lot of organizations don’t take advantage of it. FireHydrant now includes this data, giving you visibility into changes to your infrastructure while you’re investigating an incident.

Organizations need to continually ramp up and improve their security and resilience to unexpected incidents. But as the number of endpoints, networks, and user interfaces grow exponentially, the task becomes more difficult, and manual incident response management becomes less and less effective.

A common pattern in serverless architecture is to have a queue before a function. This is great because you can create a second queue for all of the messages that failed in the function execution (or, if we want to put it in terms that don’t sound like we’re aggressively shaming them, we can classify them as having “encountered an error at some point”). This second queue is known as a “dead letter queue” or DLQ for short.

BugSplat now includes local variables and function arguments for our Windows Native, Unity, and Unreal C++ integrations. By including local variables and function arguments, we can provide another level of contextual information about the cause of your crash. This new feature may help reduce or eliminate the need to debug a crash report on your local development machine.

When Patrick O’Brien interviewed to become a Site Reliability Engineer at The Trade Desk™, it was clear that taking the company’s monitoring system to the next level was the priority. “A chunk of my interview was about The Trade Desk’s previous monitoring system and how to scale it,” says O’Brien, who joined The Trade Desk more than two years ago. “I had a good feeling that would be an early task.”

Logs have been around since the advent of computers and have probably not changed all too much since. What has changed, however, are the applications and systems generating them. Modern architectures — i.e. software and the infrastructure they are deployed on, have undergone vast changes over the past decade or so with the move to cloud computing and distributed environments.