Skip to main content
Version: 0.4 · current

Sources

OverviewReviewed October 11, 2026
Applies to:Excubius 0.4Roles: Entity admin
PlansFree · Core · Pro · EnterpriseDeploymentSelf-hosted

A source is a monitoring platform Excubius reads from. Add the monitoring you already have, New Relic, NinjaOne or Azure Monitor, and its resources, metrics and alerts go through the same evaluation, Alert inbox and notifications as the checks of the native collector. Excubius never writes to a source: every adapter only reads, with the least permission each read needs.

What each source brings​

SourceInventoryMetrics that feed catalog checksAlerts
New RelicInfrastructure hosts, APM services, synthetic monitorsHost CPU, memory and disk (feed the Windows and Linux host checks); Apdex, error rate, response time, throughput; monitor success rate and failing locationsAI issues, created or activated
NinjaOneWindows, Linux and macOS devices of your organizationsMinutes since the last contact; pending operating system and software patchesTriggered conditions
Azure MonitorVMs, Azure SQL databases, managed instances, PostgreSQL flexible servers, storage accounts, key vaults, Recovery Services vaults, data factories, network gateways, firewalls and load balancersPlatform metrics and Resource Graph checks of the Azure module; Data Factory runs, triggers and integration runtimes; Key Vault and app registration secret expiryFired Azure Monitor alerts
Native collectorWhat you add as resourcesEvery other catalog checkFrom its checks

The native collector is set up by the installation and listed among the sources only for its freshness. See How the collector works.

Before you begin​

  • You need the Entity admin role on the entity the source will belong to.
  • The source kind is switched on. Each kind has its own feature switch (sources.newrelic, sources.ninjaone, sources.azure_monitor), set by a super administrator in Settings › Instance. Settings › Sources appears when any of them is on.
  • The collector is running: it polls the sources and runs Test and Sync now.
  • For a mode with webhooks, the platform can reach the public address of the Excubius server.

Add a source​

  1. Open Settings › Sources and select Add a source, then choose the platform.
  2. Under General, enter a Name and choose the Entity its resources and alerts belong to. The entity cannot change later. A New Relic account or an Azure tenant that covers several clients is usually added once per client entity, narrowed with the entity filter, the organizations or the subscriptions.
  3. Under Connection, enter the fields of the platform. Secrets are write-only: once saved they show as stored and can be replaced or removed, never read back.
  4. Under Ingest mode, choose Hybrid (recommended), Polling or Webhook only. Ingestion modes explains when each fits.
  5. Optionally, change the Polling intervals. Empty fields keep the defaults shown.
  6. Select Create source. In a mode with webhooks the page now shows the webhook URL once: copy it into the platform right away. Only a hash of its token is kept. If you lose it, Rotate URL makes a new one and the old one stops working at once.
  7. Select Test to check the credentials and what they can read; every permission is listed, and optional ones are marked. Select Sync now to run inventory, metrics and alerts at once instead of waiting for the schedule.

How source data meets the rest​

  • One resource per thing. A host reported by New Relic, by NinjaOne and by the native collector is one resource. Sources match by their own ID first (New Relic entity GUID, NinjaOne device, Azure resource ID), then by fully qualified name and host name, in the source's entity and below, and only between compatible types. A Windows host, a Linux host and an Azure VM are the same family.
  • Catalog checks, not vendor thresholds. Vendor metrics feed catalog checks, so thresholds, for durations, entity overrides and the inbox work as for native checks. The check appears on a resource the first time the source reports it. A check the native collector already runs, with a success in the last 24 hours, is never taken over by a source, and neither is a check another source feeds or one a user switched off.
  • Vendor alerts are alerts of their own kind, one per vendor rule and resource, with a link to the vendor. They resolve when the vendor says so, by webhook or when a complete poll no longer lists them. An alert you resolve by hand is not reopened by the next poll. A vendor alert whose resource is unknown stays attached to the source.
  • What disappears is marked, not deleted. A resource that a complete inventory no longer lists is missing and keeps its history.
  • Switching a source off stops its polling and refuses its webhooks; what it reported stays. Deleting it removes its alerts and the resources only it reported; resources another source or the native collector also reports are kept.

What the source page shows​

ItemMeans
FreshnessFresh, Stale (no successful poll in three intervals, at least 15 minutes; for a webhook-only source, nothing received for a day) or No data yet
Last sync, Last errorWhen it last ran, and the last error with its kind, such as Credentials refused, Missing permission or Rate limited
PhasesInventory, Metrics, Alerts and Alert reconciliation, each with its interval and last result
CountsResources, missing resources, open alerts and checks fed
WebhookWhat was received, duplicated, rejected or failed, and the recent events

What each error means and how to fix it: Collector errors.

In this section​