More than 17 million developers use Docker to build, ship, and run applications separate from their infrastructure in order to deliver software faster and more efficiently. With the rising popularity of containerized applications, however, it has become increasingly more complex and difficult to observe and monitor applications running across multiple containers.
Kentik brings real-world business context to the telemetry we collect and the analytics we provide. That’s the overarching theme I got from Networking Field Day: Service Provider 2. As I watched and listened to each presentation, it was pretty obvious to me that Avi, Steve, Doug, and Nina, all technical powerhouses, were a little less focused on packets and a little more focused on how we can improve network operations and a service provider’s ability to make smart business decisions.
Cloud services have skyrocketed in popularity in the past few years, providing a vast array of resources as well as a cost-effective path for the migration from on-premises servers to the cloud. In fact, cloud services are handling all the computing needs of many businesses. It’s very likely you’re already using cloud services and will continue to use more as time goes on.
Cloud native and microservice architectures bring many advantages in terms of performance, scalability, and reliability, but one thing they can also bring is complexity. Having requests move between services can make debugging much more challenging and many of the past rules for monitoring applications don’t work well. This is made even more difficult by the fact that cloud services are inherently ephemeral, with containers constantly being spun up and spun down.
What do a sinking ship and an improperly equipped data center have in common? For Dell Senior Director of Global Network and Datacenter Services Paul Beninati, the two have a lot in common. At least, from the perspective of company proactivity and ITOps performance goals.
Performance monitoring is an essential part of development. It’s usually one of the first things you’d want to do after setting up an existing project or getting started with a new one. Without monitoring performance, it will be challenging to detect post-development (production issues) issues in your application or how to resolve them. You may end up wasting time attempting to fix something that was never broken.
Please Note: The following article details the experience one of our partners had using MarketBuilder. As such, individual results may vary. When asked about N-able MarketBuilder, George Ioannides’ response is effusive: “I love it.” Although George, who owns Cleveland, Ohio-based MSP, Fidelity Systems, hasn’t yet been able to use MarketBuilder to its full potential, he’s an avid user of its social media and marketing capabilities.
