Continuum Local is an agent you run inside your own network. It exists so Continuum Link can read monitoring systems that are never exposed to the internet.

It is the on-premise half of Continuum Link and sits behind the same gate: an Enterprise licence and continuum_integrations.manage on the organisation or team.

Continuum Local has nothing to do with Continuum Cloud. It does not discover cloud resources, it has no scopes or poll runs, and it never draws on a canvas. It serves connector panels on strata.

What it serves

Seven connectors: SolarWinds Orion, Zabbix, PRTG Network Monitor, Checkmk, Icinga 2, ManageEngine OpManager and WhatsUp Gold. Each appears in the connector list but stays disabled, reading "Needs a Continuum Local agent", until your organisation has an agent that is enrolled and online. An agent counts as online when it has checked in within about ninety seconds.

How it reaches Blueprintr

The agent dials out. It long-polls Blueprintr over TLS, claims queued work, executes it against systems on your network, and posts the results back on a later poll. Nothing connects inward, so no inbound firewall rule is needed.

It is for private and firewalled estates, not air-gapped ones. A host with no outbound path to Blueprintr cannot run it.

There is no schedule of its own. A job is created when an editor refreshes a linked tab, and a queued job expires if no agent claims it.

Credentials stay on your network

Credentials for your on-premise systems are held in the agent's own configuration file and are never sent to Blueprintr. The connection form for an agent-backed connector has no credential field at all; it says "Credentials stay on your network" in its place.

Blueprintr runs the connector with unguessable placeholder values standing in for the credential, and tells the agent which parts to replace with local values. The agent refuses to send a request if a placeholder survives into it.

Blueprintr therefore cannot read, export or recover those credentials, and cannot help you rotate them. Rotation happens in the agent's configuration and in the monitored system.

Connector	Credential parts in the agent config
SolarWinds Orion	`username` and `password`
Checkmk	`username` and `password`
Icinga 2	`username` and `password`
WhatsUp Gold	`username` and `password`
Zabbix	`token`
PRTG Network Monitor	`token`
ManageEngine OpManager	`token`

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.

Registering an agent

Add an agent

Name it, and Blueprintr issues an enrolment token.

Copy the token now

It is shown exactly once, can be used once, and expires after 24 hours. An expired, spent or revoked token all fail enrolment with the same message, so mint a fresh one rather than diagnosing it.

Put it in the agent's configuration

Set it as enrollmentToken in the agent's config.json, start the agent, then delete that line. It is spent once used.

Copy the connector configuration

The panel prints a configuration block for each connector, keyed by the connection's ID. This panel is the only place in Blueprintr that shows that ID, so setup cannot be completed without it.

New token and Re-enroll mint a replacement, which burns the previous one. Revoke cuts an agent off. An enrolled agent that does not advertise HTTP relay shows "Does not advertise HTTP relay", meaning it needs upgrading.

Compatibility

The agent advertises what it can do, and Blueprintr sends only work that matches. A newer kind of job is invisible to an older agent rather than breaking it, so agents upgrade on your schedule rather than Blueprintr's.

Certificates

A self-signed certificate is a frequent cause of a failed on-premise connection. Orion, PRTG, Checkmk, Icinga 2, OpManager and WhatsUp Gold all ship one. Point the agent at your certificate authority file rather than disabling certificate checking.

Getting the agent

The agent is not yet available to download from Blueprintr. Registering an agent and copying its configuration both work, but obtaining the software itself needs your account contact. Ask before planning a rollout around it.