Alerts on a diagram

Alert state from a linked monitoring platform appears on a stratum, as a saved panel. It never appears on the drawing.

On the stratum, not the canvas

Shape outlines do change, but they come from Continuum Cloud discovery, not from monitoring. A red outline means the cloud provider reports the resource offline, not that something is alerting. The full vocabulary is on keeping diagrams true.

To see where in a system a problem sits, open the stratum for the component. The diagram gives it its context; the panel gives it its state.

Who can read it

The saved panel travels with the stratum. It is stored in the blueprint's own record and in backups, and unless the connector restricts its audience to editors it reaches everyone who can read the blueprint, including anonymous readers of a public blueprint, embeds and exports.

Among the alerting and monitoring connectors, only Datadog, LogicMonitor, Auvik and Rootly can restrict it, and a new connection to any of them starts restricted. A Datadog or LogicMonitor connection created before the setting existed stays reader-visible until an administrator changes it. Check the connector before linking an alerting platform to anything published. See Continuum Link.

What a panel is

A dated snapshot, fetched when an editor asked for it. Opening the tab displays what was saved and contacts nothing.

Read the banner above it before acting on the numbers. It says whether the snapshot is current, due a refresh, incomplete, failed or paused. An incomplete snapshot reports lower bounds, and a failed read is labelled unavailable rather than shown as zero.

Counts describe what a platform reported at a stated time. They are not a statement that a component is healthy now.

Finding which platform knows about a shape

Each aid needs an Enterprise plan, edit access, and at least one verified connection. Below that they refuse or do not appear.

Suggest Continuum Links under a Vellum diagram's bottom bar checks every shape on the blueprint against Blueprintr's index of your connections, and the button says how many matches it found before you open it. The same button on a stratum's tab strip checks one stratum: its linked shape, its title, and hostnames, addresses or URLs in its text. Check live in either dialog asks the connections themselves instead, a batch of shapes at a time. Matches with strong, unambiguous evidence start ticked. The rest are listed with the reason they were held back, which includes an index that is out of date, incomplete, or limited to some object types. A connection a stratum already links is not suggested for that stratum again. See Continuum Link for what the index stores and when it updates.

Right-click a shape in a saved diagram and choose Suggest integrations…. It scores matches from the shape's identifiers, its icon, and whether a connected shape is already bound to the same platform.

On Details and files in the blueprint editor, the scan button reads Scan · N integrations once connections exist. It reads stratum titles, file content, tab bodies and shape labels, up to 200 identifiers per scan.

All of them propose candidates for review and attach nothing until you add or apply them.

Not a monitoring system

Blueprintr does not evaluate conditions, hold thresholds, or page anyone. It reads state from the system that does, and links back to it for anything you need to act on.