Operations | Monitoring | ITSM | DevOps | Cloud

There are a number of growing pains every business experiences, especially when that growth is hectic. And especially when there are so many moving parts in a business, things like licensing, rapid cloud spending, legacy applications, and tool sprawl may not be at the forefront of everyone’s mind.

If a problem reached you, it means nobody else could solve it. That makes it worth documenting — right then, while you're in it. Six months from now, your team will thank you. Watch the full IT Leadership Lab session.

IT documentation doesn't have to be a wall of jargon. Here's how to use AI to compress technical information into user-facing docs that are clear, fast, and actually useful.

Business metrics should inform almost every other metric that's being evaluated.

Documentation may not be the most glamorous thing in the world, but it can not only save your vacation, but also make processes more efficient, enable employees to problem-solve on their own, and allow you to do more important things. In this stream, we discuss.

If you start making individual metrics public, you create a culture of individuality rather than collaboration.

NinjaOne Field CTO, Jeff Hunter, demonstrates how to automate the vulnerability importation from Microsoft 365 into NinjaOne. While this process can be automated using Microsoft Azure Functions or AWS Lambda, for the purposes of this demonstration we will be using an API server. Chapters.

In this stream, we talked with Nate Payne, an expert in all things IT leadership, to discuss how you can build an IT metrics framework that aligns with organizational goals and keeps you from continuing to measure obsolete metrics.

NinjaOne Field CTO Jeff Hunter shows how to set up an API server. An API server is a framework for securely integrating data from other services into NinjaOne. One example (and next week's video) would be retrieving current CVE data from a third-party vulnerability scanner and regularly importing that CVE data into NinjaOne for visibility and remediation. Chapter Markers.

Deployments that need multiple reboots shouldn't need a technician hovering over them the whole time. But for most teams, that's exactly what happens — you kick off a job, walk away, and come back to find it stalled halfway through waiting for something nobody handled. Product Manager, Dan Myers, joins this stream to show how these new updates changes enterprise-scale provisioning and deep OS deployments, making your automation smarter than ever before. What you'll learn.