Operations | Monitoring | ITSM | DevOps | Cloud

Project schedule management is essential to the successful completion of any project. By mapping out a clear schedule, you can hold team members accountable to deadlines for specific tasks and ensure projects are completed within agreed timeframes. You can use project schedule management software to outline key milestones and assign team members to complete certain tasks.

Traditionally, most organizations have had siloed departments wherein teams’ activities are highly separated and the objectives within organizational structures are divided. This operational methodology has brought about friction – especially within the IT department, where developers and ITOps lack collaboration.

NinjaOne released our custom field functionality in 2021, adding a new level of flexibility, customization, and automation power to our platform. Custom fields are an advanced feature that requires setup to use, but once you start, the power and flexibility of this feature is almost limitless. In this blog piece, we’ll walk you through a powerful use case for custom fields in NinjaOne. Refer to part one of this series for a quick overview of NinjaOne Custom Fields.

How do you know your SQL Server system is running well? Is it the simple method of noting no one is complaining? (Sadly, in many businesses, this is exactly how it's done.) The fact is, if you're not monitoring SQL Server performance, you don't know.

Most support organizations today adopt some form of the traditional tiered support model. It is one that is based on a process of escalations and customer handoffs. Under this model, customer issues get escalated through multiple levels of a support hierarchy, with three tiers being a common workflow.

Traditionally, applications are developed and deployed on local servers managed by developers. This keeps the whole process under the control of one development team that is responsible for keeping the system running smoothly. With serverless computing, however, the server management and code execution within applications takes place remotely, under the control of the cloud service provider rather than an in-house development team.

The term Site Reliability Engineer (SRE) first appeared in Google in the early 2000s. In Google’s 2016 SRE Book, Benjamin Treynor Sloss wrote that, generally speaking, “an SRE team is responsible for the availability, latency, performance, efficiency, change management, monitoring, emergency response, and capacity planning of their service(s).” This means that the SRE teams at Google decide how a system should run in production as well as how to make it run that way.

The last couple years have set new global benchmarks for the data and technology sector, putting companies that have considerably accelerated their digitisation processes in the front row. Our relationship with technology also changed immensely. One that has created new expectations by and for all stakeholders – from consumers to enterprise technology companies and governments.