Serverless technologies let us do more with less effort, time and energy. They let us focus on creating user value and let the cloud handle undifferentiated heavy-lifting like scaling and securing the underlying infrastructure that runs our code. Serverless technologies have allowed me to accomplish tasks as a solo engineer that used to take a whole team of engineers to accomplish, and I’m able to complete these tasks in a fraction of the time and cost to my customers.
Over my time as a Sales Engineer and Partner Success Manager, I quickly learned that there are a few under-utilized features of N-sight RMM. While performing RMM dashboard audits, three of these features routinely came up in conversation with our partners. They include the Site Concentrator, Data Overdue Cross-Check, and Monitoring Templates. In this blog series, we will briefly cover uses in your day-to-day work and implementation of the features.
What’s autorun? Autorun is a feature of the Masterfiles Policy Framework (MPF)1 that simplifies the process of adding and executing new policy. We have talked about Modular policies with autorun and the Augments before. This time, we dig into autorun a bit deeper to explore some of its current features and look at how to implement your own as we did during The Agent is In, Episode 15 - Extending Autorun
If you are in a room with 20 engineers and you ask, “explain what an API is to a non-technical person”, you will get 20 different analogies. An API is like the on button to your TV connecting you to a variety of shows and systems, or an API is like a waiter taking your order and serving you from the kitchen. An API is like a library card catalog, or it’s simply a tool that connects you to other tools.