RMMs and Alerting

Addigy Integration

This article provides a guide on integrating Addigy with Halo for asset management and alerting. It explains how to connect Halo to Addigy, set up asset imports on a schedule, and manage alerts. The integration can synchronize assets and generate alert tickets, with assets imported using the Halo integrator to ensure details are up-to-date. The guide covers the connection process, obtaining API credentials, and configuring asset mappings. It also includes instructions for either automatic asset import or alert processing using the Halo integrator or webhooks, depending on the API version used.

Atera RMM Integration

This article provides a guide on integrating Atera RMM with Halo for efficient management and synchronization of customer and device data. It details the steps for connecting the systems, importing customers and assets, and setting up automatic data syncing. The integration enables seamless management of alerts, creating tickets in Halo when an alert is triggered in Atera and resolving alerts and tickets across both platforms. Instructions on enabling the integration and configuring alert processing are also included for effective monitoring and management.

Auvik Integration

This article provides a comprehensive guide on integrating Auvik with Halo, detailing steps for generating an API key, configuring general settings, and mapping sites, networks, and devices between the two platforms. It covers the option to import and manage assets, enabling alert systems via webhooks, and specifying authentication methods such as Basic Authentication and OAuth 2.0. The article also includes instructions for setting up a webhook and associating alerts with notification channels in Auvik. Troubleshooting tips are provided for resolving common import errors.

Azure Monitor Integration

This guide explains the process of integrating Azure Monitor with Halo. It involves setting up webhooks for sending alerts from Azure Monitor to create tickets in Halo, configuring field mappings, and ensuring resolved alerts automatically close tickets. To connect, users must enable the integration in the asset management and alerting configuration, set up the webhook URL for authentication, and enable the common alert schema. The guide includes steps for default ticket setup, user and status configuration, and mapping fields from Azure alerts to Halo custom fields.

Azure Sentinel Webhooks

This article provides a guide on setting up webhooks in Azure Sentinel for ticket creation in Halo. It includes steps to create a Logic App in Microsoft Azure using the Multi-tenant Consumption hosting option, add triggers, and configure HTTP actions. Sentinel Automation Rules are also set up, with automation rules created for incident creation and updates, allowing the playbook to send requests to the Halo API. This setup is available from version 2.182.1 onwards.

Barracuda RMM

The article details the integration between Barracuda RMM and Halo to efficiently manage devices, customers, sites, and alerts. It covers the process of enabling and configuring the integration, mapping Barracuda sites and VAR domains to Halo sites and customers, and importing assets. The guide also instructs on setting up automatic syncing for assets and alerts and outlines the procedures for managing alerts from Barracuda within Halo, ensuring seamless operation between the two platforms.

Cisco Meraki Integration

This article provides a comprehensive guide on integrating Cisco Meraki with Halo. It details steps for enabling the integration, connecting using an API key, and configuring imports for customers and assets. The guide also covers setting up alerting through webhooks, allowing events in Cisco Meraki to automatically log tickets in Halo. Additionally, the article explains asset field mappings, determining asset types, import scheduling, and processing webhooks either by default methods or through the Event Management module for enhanced control and security.

Cloudflare Integration

ConnectWise Automate Integration

This article guides users through integrating ConnectWise Automate with Halo for remote device management. It covers user credentials, module configuration, client and asset imports, and alerting setup. Users need to configure an Integrator User to bypass MFA. The module is enabled through the configuration section in Halo, where users enter server URL and credentials. The process includes importing clients, sites, users, and mapping asset types. Alert configurations are also addressed, enabling email alerts and handling ticket updates from ConnectWise. Specific permissions for API-based alerting are required.

ConnectWise RMM Integration (Asio Platform)

Connectwise RMM Integration Guide

This article provides a guide for integrating ConnectWise RMM with the Halo system. It covers the steps to connect Halo to ConnectWise, import sites and assets, configure alerting systems, and sync data between the two platforms. Users will learn how to set up authentication, manage asset and site imports, configure webhooks for alerting, and use API tokens for secure communications. The document also details how automatic scheduled syncing can be activated, ensuring continuous data updates between Halo and ConnectWise RMM.

Coralogix Integration

CyberCNS (Cyber CNS) Integration

Datadog Integration

This guide provides a comprehensive overview of integrating Datadog with Halo to manage alerts. It covers the steps to connect to Datadog, including setting up authorization applications and creating webhooks for both monitoring and security alerts. The article also details custom-configuring alert tickets in Halo by editing payloads to include various ticket types, users, and custom fields. Additional configurations for security alerts allow changing alert statuses directly from Halo. Overall, this integration aims to streamline alert management within a single platform.

Datto RMM Integration

This article provides a comprehensive guide on integrating Datto RMM with the Halo platform. The integration allows automatic import and synchronization of assets and sites from Datto into Halo, with options for remote access and alerting. Key steps include enabling API access in Datto, configuring customer and site imports, setting up asset field mappings, and defining asset types and matching criteria. The guide also covers setting up scheduled imports and alerting via email or webhooks, including necessary configurations and troubleshooting tips.

Dynatrace Integration

Event Management

This guide outlines how to set up and manage event management platforms in Halo. It includes instructions on creating event rules to determine when events log tickets and how they populate ticket fields. Event management allows integration with Asset Management systems using webhooks. Users can match events to update existing alert tickets or create new ones. The guide also details how to authorize webhooks, define variable criteria for events, and manage alert creation. Other functionalities include customer, site, user, and asset matching to enhance ticket management processes.

General Procedure for Integrating with an RMM

Heimdal Integration

Juniper Mist Integration

Kaseya VSA Integration

This article provides a guide on integrating Kaseya VSA with Halo to import and sync assets, customers, and alerts. It details obtaining OAuth 2.0 credentials from Kaseya, configuring the integration by entering credentials in Halo, and setting up redirect URLs depending on your Halo version. The Kaseya VSA Integration works primarily with Halo for syncing alerts, and offers instructions for importing clients and assets. The article also covers how to adjust field mappings and asset type overrides during setup.

Keeper Integration

LogicMonitor Integration

N-Able N-Central Integration

This article provides a comprehensive guide on integrating N-Able N-Central with Halo. The integration enables the import and sync of customer and asset information, alert management, and scheduled imports. The guide covers connecting to N-Central, setting up customer and asset mappings, importing from N-Central, and configuring alert management using webhooks. Miscellaneous settings and common error resolutions are also included to ensure successful integration and ongoing operations.

N-Able N-Sight RMM Integration

This article provides guidance on integrating N-Able N-Sight RMM with Halo. It covers key steps such as generating an API key, configuring the module, and importing customers, sites, and assets. The integration enables alerting functionalities and the use of the Halo Integrator for automatic syncing. Users are instructed on mapping fields between systems and configuring alerts to ensure communications and data exchanges are effective. The article emphasizes the importance of configuration checks to ensure seamless integration.

Nagios XI Integration

The guide explains how to integrate Nagios XI with Halo to generate tickets for alerts. It details the steps to enable the integration, create passwords, and map alert statuses to ticket priorities. Users must set up outgoing webhooks in Nagios XI for Host-Alert and Service-Alert events to send data to Halo. This data generates tickets and matches them using fields like 'metric_name', 'problem_id', and 'hostname'. Alerts are updated as actions in the ticket, with 'Up' and 'Ok' statuses resolving alerts and closing tickets.

New Relic Integration

This article provides a comprehensive guide on integrating New Relic with Halo for managing incidents. It explains two integration methods: the legacy Halo Integrator and the current Webhooks method. The integration allows incident management between New Relic and Halo by auto-generating tickets in Halo for New Relic alerts, which can be resolved in either platform. The guide details setup steps, including obtaining and using API keys, enabling modules, and configuring webhooks for faster alert processing. It also covers setting ticket types, user assignments, priority mappings, and viewing alerts.

Ninja Systray Icon

NinjaOne Integration

The NinjaOne Integration guide explains how to integrate NinjaOne with Halo, enabling import and synchronization of customers, assets, and alerts. It includes steps for configuring the NinjaOne module, setting up authentication, importing organizations, locations, devices, and software, and managing alerts using the Halo integrator or webhooks. The guide also covers user matching, field mapping, and the use of Halo Integrator for scheduled imports. Additionally, it explains configuring webhooks in NinjaOne and how to enable automation policies in Halo.

PRTG Integration

Rapid7 Integration

The article provides a guide on integrating Rapid7, covering what the integration entails, how to enable the Rapid7 module, connect to Rapid7, and utilize runbooks. The Rapid7 integration supports runbook-based ticket creation and alert management. To enable, navigate to Configuration > Integrations > Asset Management and Alerting and activate the module. Once enabled, relevant runbooks will be added to your instance for easy access. The guide includes sections on connecting to Rapid7 and specific runbooks available for use.

Reconciliation - Order of Precedence for CMDB/Asset Integrations

RMM/Alerting Integrations Comparisons

The article compares various RMM/alerting integrations focusing on their functionalities with Halo. It lists features like importing customers, assets, and alerts processing methods. It also discusses user and asset alert matching, and integration capabilities such as creating shortcuts to integrated tools. The article clarifies terms like import, user matching to assets, multi-tenanted integration, and alert matching. For detailed setup guidance, it refers to dedicated articles on each tool including N-Able N-Central, NinjaOne, Datto RMM, Auvik, Cisco Meraki, N-Able N-Sight RMM, and Atera RMM.

SaaSAlerts Integration

SCOM Integration

The article provides a comprehensive guide on integrating SCOM with Halo for alert management. It outlines steps for enabling the integration by configuring both SCOM and Halo settings, such as adjusting SCOM alert templates and using the Halo interface for asset and alert configuration. Additionally, it details the process for resolving alerts automatically in SCOM through the Halo integrator application, offering guidance on authentication, deployment, and choosing between different integrators based on security needs. Recommendations and related settings for managing client access and scheduling imports are also included.

Site24x7 Integration

The article guides users on integrating Site24x7 with Halo to automate alert ticket creation. It includes steps for enabling the integration, configuring webhooks in Site24x7, and setting ticket creation parameters in Halo. Assets can be matched using specific fields, and the integration supports managing tickets by triggering and testing alerts. It ensures ticket creation when services are down, allowing updates based on Site24x7's status and automatically closing tickets when services are up again. Users can run a specific report to view webhook activities related to Site24x7.

SolarWinds Orion Integration

The article provides a comprehensive guide on integrating SolarWinds Orion with Halo. It explains the prerequisites for integration, such as using SolarWinds Orion version 2020.2 or later, and details the configuration process to enable and set up the integration. The integration allows automatic creation and management of alert tickets within Halo, linking them to specific agents, teams, and assets. It discusses how to configure trigger and reset actions, receiving and updating alerts, and the use of Halo Integrator for communication with SolarWinds API. The guide also covers password storage options and client ID restrictions for enhanced security.

Splunk Integration

The article provides a comprehensive guide on integrating Splunk with Halo to automate the logging of alerts as tickets. It covers the setup process, including enabling the integration module, configuring webhook processing types, and authenticating webhooks. Users can create webhooks for Splunk alerts and view detailed alert results from Halo. Different processing methods are explained, with specific instructions for adding URLs to Splunk's webhook allow list. The guide aims to streamline alert management for technicians by synchronizing Splunk alerts within Halo.

Super Ops RMM Integration

SyncroMSP Integration

The SyncroMSP Integration with Halo enables the import of customer and asset data from SyncroMSP, automatically syncing updates and supporting alert management. Users can connect the integration by enabling the module, configuring connection settings with an application URL and API key, and importing customers and assets. Customers and assets are matched and mapped between systems. Automatic synchronization can be set up for ongoing updates. The integration also allows for alerting, where alerts in SyncroMSP create tickets in Halo and are managed across both systems via webhooks.

Tanium Integration

Triggering Automation Policies in RMM via Halo

WatchGuard Integration

Zabbix Integration