NinjaOne provides intuitive endpoint management software to managed service providers (MSPs) and IT professionals. The dashboards provide a single pane of glass for all devices running agents in your infrastructure. NinjaOne alerts can be forwarded via email and through their API. These tools are useful however for critical alerting that needs immediate attention in the middle of the night is where SIGNL4 comes in. Data breaches, security violations and potential mission critical threats are identified sooner and resolved quicker, reducing downtime, and saving money! Persistent notifications and tier escalation within SIGNL4 ensure that critical alarms are not missed. Issues are taken beyond the dashboard and inbox and delivered vis Push, SMS, and Voice.
How it Works
The SIGNL4 team receives NinjaOne alert notifications via email and/or webhook then alerts on-call duty members of the issues in real time using push, SMS and voice.
Tickets and Incidents are sent to SIGNL4
Event categorization, routing and automated delivery
Persistent Notifications by push, text and voice call with Tracking, Escalation and Confirmation to Staff on Duty
HOW TO INTEGRATE
In our example we are forwarding a NinjaOne alert of a print spooler being down to our SIGNL4 account. Details about the alert will be sent immediately to the SIGNL4 to quickly notify users of the problem.
SIGNL4 is a mobile alert notification app for powerful alerting, alert management, and mobile assignment of work items. Get the app at https://www.signl4.com
A SIGNL4 (https://www.signl4.com) account
A NinjaOne (https://www.ninjaone.com) account
To start this integration, we setup a VM on the Azure network and then installed the Agent provided by NinjaOne.
Immediately we started to see the server metrics. We are using the preconfigured Print Spooler policy to trigger alerts.
The first integration method was via email. We created a user within NinjaOne and gave this user the SIGNL4 team specific email address. Configuring the user to receive all alerts regardless of severity.
We then stopped the Print Spooler and the alert was sent directly to SIGNL4.
Next, we wanted to explore the API capabilities. We registered the team specific webhook for SIGNL4 using the provided documentation from NinjaOne. https://resources.ninjarmm.com/API/Ninja+RMM+Public+API+v2.0.5+Webhooks.pdf
We preformed a restart of the Print Spooler service and ran the test again. Immediately we received the alert with the JSON payload separated out into an easy to read format within SIGNL4.Example of NinjaOne email.
SIGNL4 can further increase the visibility of alerts through its Signals and Services section. Augmenting the color and icon of alerts will provide more relevant information at a glance without having to open the alert.