Operations | Monitoring | ITSM | DevOps | Cloud

While auditing the Kubernetes source code, I recently discovered an issue (CVE-2020-8563) in Kubernetes that may cause sensitive data leakage. You would be affected by CVE-2020-8563 if you created a Kubernetes cluster over vSphere, and enabled vSphere as a cloud provider with logging level set to 4 or above. In that case, your vSphere user credentials will be leaked in the cloud-controller-manager‘s log.

A hybrid infrastructure strategy is integral in creating a successful digital transformation in your enterprise. Programmable infrastructure (PI), or Infrastructure as Code, makes these strategies work in the real world. This blog will cover some highlights from the Gartner Report on why I&O leaders must adopt programmable infrastructure to enhance customer-focused agility.

As defined by ITIL an ‘Incident’ is an unplanned disruption or reduction in quality of service and a ‘Problem’ is the underlying thing that caused the Incident. They are obviously related and there are endless pages on the internet going into incident and problem management as part of ITSM, so we won’t delve into this topic in any detail. The key issue is resolving the incidents themselves isn’t always enough, you need to get to the route cause of the problem.

If you’re building applications and running services in Microsoft Azure, SquaredUp for Azure is a presentation layer that sits on top of the Azure APIs enabling you to produce effective, informative and engaging dashboards.

Amazon Web Services and Microsoft Azure do not need any formal introduction. They are two major players in the cloud computing and virtualization industry. AWS leads with about 32% market share. On the other hand, Azure is the next closest with about 17% market share. Both the tech giants, AWS and Azure, have been on an onward growth trajectory with revenue boosts coming in every quarter.

Modern networks are complex beasts. With this complexity comes many opportunities for things to go wrong. Additionally, networks are often the backbone of businesses, and so when they don’t perform to the best of their capabilities, your business may suffer. As a network administrator, this is certainly something you’d rather avoid. One of the best ways to avoid business-impacting issues is to see them coming and fix them before they have a chance to wreak havoc.

Anyone who’s worked in IT knows a great deal of the day-to-day work doesn’t come down to one secret trick—the job consists mainly of stringing together hard-won wisdom and convenient Google searches to solve problems. Working in IT is a little like parenting; when you’re first told you need to pick up your children’s LEGO bricks every day, you say, “Really? Is it really necessary to do it every single day?” But you only have to step on one at 1 a.m.

In my last post, we talked about the Android Enterprise features that are going to be the most useful in supply chain. (If you missed it, you can see it here: The Most Important Android Enterprise Features for Supply Chain.) Those are aspects of Android Enterprise that are going to make your life easier. However, to get there, we have to go through a bit of a hard transition.

Recently, Catchpoint participated in the virtual Networking Field Day. As a presenting sponsor, we spoke about the importance of network monitoring and the shift in enterprises’ strategic initiatives supporting user experience monitoring. For an hour, the discussion focused on how the digital experiences for employees and customers are converging. Enterprises are shifting to measure and monitor the tenets of reachability, availability, performance, and reliability.

Apply rules simplifies creation of objects like Service, Notification, Dependency, ScheduleDowntime which require object relation. In this blog post we will understand rule based monitoring with Icinga apply rules with examples.