Operations | Monitoring | ITSM | DevOps | Cloud

We are thrilled to announce that NinjaOne has been named the “Best Emerging Vendor” at the prestigious 2023 Britain’s Reseller Choice Awards. This achievement highlights NinjaOne’s significant impact in the IT sector and its rapidly growing influence within the British market.

Got cybersecurity problems? Well, the good news is the same as the bad news — you’re not alone. The world of security has a big data problem and an even bigger people problem. Enterprise connectivity has drastically increased in the last decade, meaning every employee, contractor, and vendor has some level of access to corporate networks. To support this growth, companies monitor exponentially increasing infrastructure and traffic, producing a steadily rising volume of data.

In recent years, IT departments have faced the challenge of adapting to an evolving landscape of demands. While the primary focus of traditional incident management solutions has been to reduce downtime, it's become clear that just reducing the amount of downtime isn’t sufficient. To truly mitigate the total impact of downtime, there must be a focus on reducing the damage and costs that accumulate while you are down.

Time and time again we hear the same statements from FinOps teams with respect to what is holding back optimization of wasteful cloud resource consumption. Engineers and App Owners are interested in helping but stop short at actually taking actions to reduce that waste. There are many reasons for this main sticking point when it comes to application owners and developers taking action.

PCE is a performance metric that evaluates the effective utilization of power in data centers. It measures the ratio of IT equipment power to the total power consumed, encompassing all aspects of the facility’s operations, including cooling and lighting. Unlike traditional metrics, PCE provides a comprehensive assessment of how power is used within data centers, aiming to optimize the actual power capacity available.

Naturally, our own platform forms the backbone of our cloud cost savings strategy. And before releasing any new feature, we try it out ourselves to see how well it helps us manage our own SaaS costs. If it works well for us, that means there’s already one satisfied user in the world — and there will likely be more!

As enterprises grapple with the evolving landscape of security threats, the need to safeguard internal networks from the broader internet is increasingly important. In environments with restricted internet access, it can be difficult to manage software updates in an easy, reliable way. When managing devices in the field, change management and compliance policies can introduce even more complexity to the update process. You can solve these challenges using snaps and the Snap Store Proxy.

“Are your customers, partners and employees complaining about how slow your applications are running?" If you are not worried about the answer to this question, stop reading now.

The border between the management of telecommunications networks and the services that they support and the management of IT infrastructures and the applications that they support has always been a porous one. One might say that they are like two dialects of the same language rather than different languages. Nonetheless, these areas, whether characterised by technology or practice, are different and have, for the most part, been served by different vendors and products.

As we’ve talked about before, our app is a monolith: all our backend code lives together and gets compiled into a single binary. One of the reasons I prefer monolithic architectures is that they make it much easier to focus on shipping features without having to spend much time thinking about where code should live and how to get all the data you need together quickly. However, I’m not going to claim there aren’t disadvantages too. One of those is compile times.