38 connectors are registered. 28 connect directly, 7 need Continuum Local, and 3 are declared but not built. All of them need an Enterprise licence and continuum_integrations.manage, and none of them draws on a canvas.

Every connector can be found by free-text search when linking a stratum. Where a credential field has no label of its own, the form calls it API token.

Alerting and on-call

Connector	Credential	Other fields	Panel
PagerDuty	API token	PagerDuty region, Imported content	Service identity, open incidents, incident coverage, ownership, on-call coverage, related services
incident.io	API key	Catalog types, relationship fields, attributes, history days, remediation counts	Catalog entry and related incidents, or one incident with durations and follow-ups
Rootly	API key	Content audience, ownership context, on-call coverage, action item counts	Service response and history, or one incident's lifecycle
Jira Service Management Operations	Atlassian sign-in	Site, counts-only	Alert scope with open, unacknowledged and snoozed counts, or an on-call schedule
FireHydrant	API key	None	Service tier and active incidents, or one incident
Splunk On-Call	API credentials (JSON)	None	One incident, paged teams and state transitions
xMatters	Password	Instance URL, Username	A group, a person or an event, with recent events

Observability

Connector	Credential	Other fields	Panel
Datadog	Datadog credentials	Datadog site, content audience, saved detail, approved tag keys, Software Catalog, SLOs, default SLO window	Host, monitor, catalog service or reliability objective
New Relic	User API key	Region (optional)	Entity identity, alert severity, reporting state and tags
Dynatrace	API token	Environment URL	Entity identity and open problems by category, with a timeline
Elastic Observability	API key	Kibana URL	Alert rule identity, active count and execution status
Splunk Observability Cloud	Access token	Realm	Detector state, active incidents by severity, current signals
Grafana Alerting	Service account token	Grafana URL	Firing alerts for a label matcher, or one alert rule's state

Every cloud connector reaches its provider from Blueprintr over HTTPS and is blocked from private, loopback, link-local, carrier-NAT and metadata addresses. Any URL field in these tables must name a publicly reachable host: Grafana, Alertmanager, Kibana, Dynatrace environment, self-hosted GitLab, xMatters and ServiceNow included. An internal host needs one of the on-premise connectors below, and Grafana, Alertmanager, Elastic, Dynatrace and GitLab are not among them.

Monitoring

Connector	Credential	Other fields	Panel
LogicMonitor	Bearer token	Company, content audience, saved detail, group scope, maintenance context, instance datapoints	Device, DataSource instance or resource group
Auvik	API key	Region, Username, site scope, audience, saved detail, alert history period, optional sections	Device context and recent alert history
AWS CloudWatch	None	A verified AWS cloud connection and a region	An alarm with recent state changes, or a log group with event volume
Azure Monitor	Client secret	Tenant ID, Client ID, Subscription ID	Resource identity, alerts by severity, recent alerts
Google Cloud Monitoring	Service account key (JSON)	Project ID	Alert policy and its conditions
Prometheus Alertmanager	Password	Alertmanager URL, Username (optional)	Alert counts for a matcher, top labels, firing since

CloudWatch is the one cloud connector that stores no credential of its own. It reuses a verified cloud connection, so the form offers a connection and region picker instead of a token field.

That connection's role needs nine CloudWatch and Logs actions the discovery role does not grant. The form lists them under Required IAM actions for the backing role; add them before expecting alarm or log-group data. On an organisation-mode connection the form also asks for a 12-digit member account id.

Alertmanager always requires a secret to save the connection. For an unauthenticated instance, leave Username blank and type any placeholder in Password. It is never sent without a username.

Google Cloud Monitoring shows alert-policy configuration only. Its panel states "Open incidents unavailable".

Uptime and synthetics

Connector	Credential	Other fields	Panel
Pingdom	API token	None	Check identity, uptime percentage, average response, state changes
Better Stack Uptime	API token	None	Monitor identity, SLA and incident counts, active incidents
UptimeRobot	API key	None	Monitor identity, recent health and window totals
Checkly	API key	Account ID	Check identity, sampled results, latest runs
Site24x7	OAuth credentials (JSON)	OAuth client ID, Data centre (optional)	Monitor state, account-wide fleet status, current problem monitors

Service management and source control

Connector	Credential	Other fields	Panel
Jira Cloud work items	Atlassian sign-in	Site, counts-only	One work item, a saved filter or a JQL scope
ServiceNow CMDB	Password	Instance URL, Username, Snapshot audience, Saved detail, Open work	Configuration item with lifecycle, environment, ownership groups and discovery dates; relationships from the CI's side with the total; optional open incident and change counts
GitHub	Access token	Organization (optional)	Repository identity, activity, recent issues and workflow runs
GitLab	Access token	Instance URL (optional)	Project identity, activity, recent issues and pipelines

GitHub and GitLab take a pasted access token. There is no sign-in button on the Continuum connection form; Jira is the only connector that signs you in.

On-premise, through the local agent

These seven appear in the connector list but cannot be selected until the organisation has an enrolled agent that is online. Until then the option is disabled and reads "Needs a Continuum Local agent". Their credentials live in the agent's own configuration and are never sent to Blueprintr, so the connection form has no credential field.

Connector	Credential parts in the agent config	Other fields	Panel
SolarWinds Orion	`username` and `password`	Orion server URL, Orion username	Node identity, health metrics, active alerts, interfaces, volumes
Zabbix	`token`	Zabbix frontend URL	Host identity, unresolved problems, current problems
PRTG Network Monitor	`token`	PRTG server URL	Device identity, sensor counts, unhealthy sensors
Checkmk	`username` and `password`	Checkmk URL, Site, Automation user	Host identity, service states, current problems
Icinga 2	`username` and `password`	API URL, API user	Host identity, service states, active problems
ManageEngine OpManager	`token`	OpManager URL	Device identity, active alarms
WhatsUp Gold	`username` and `password`	WhatsUp Gold URL	Device identity and active monitor counts

For SolarWinds Orion, Checkmk and Icinga 2 the username typed into the connection form is replaced by the agent's own at dispatch, so set it in the agent config.

Declared but not built

NetBox, Infoblox and Veeam Backup & Replication appear in the connector list as disabled options marked "On the roadmap". They cannot be connected.

Reading any panel

Whatever the connector, the same rules hold.

Data is fetched with the connection's credential, not the reader's. A source link opens the provider, which applies its own permissions.
A panel is a named projection of the provider's response. The raw upstream object is never stored as-is.
A failed read never becomes a zero. Sections are marked unavailable or partial, and partial counts are lower bounds.
A provider that cannot be reached leaves the saved snapshot in place. The tab keeps its last successful body and the banner reads "Last refresh failed". A first link that cannot fetch is refused, so no tab is created.
A saved panel reaches everyone who can read the blueprint unless its connector has an audience setting. Only Datadog, LogicMonitor, Auvik, Rootly and ServiceNow have one. On a public blueprint every other panel is visible to anonymous readers, embeds and exports.
Counts describe what was retrieved at the stated time. They are not a statement that the component is healthy now.

Connector reference