Connect Affinity

The Affinity integration connects supported provider inventory and readings to a SanSignal project. Availability depends on platform enablement, provider access, and the supported profiles discovered for your assets.

Prepare the external connection

An organization administrator configures the Affinity tenant and REST identity, plus a dedicated, pre-provisioned Service Bus subscription for SanSignal. REST access and the receiver connection have separate readiness and runtime-health checks.

Complete the readiness steps shown in the connection setup, including the required broker policy information. An empty subscription by itself does not establish readiness. Use the connection’s diagnostics to understand whether REST access, receiver access, or a prerequisite needs attention.

The administrator then grants the project access to the connection and the relevant discovered Affinity site. A project pipeline chooses its own destination SanSignal site.

Browse provider data

The Affinity Browser lists sites granted to the project and their REST browsing readiness. Open a ready site to explore provider metadata and its current SanSignal mappings. The catalog uses a saved metadata snapshot; authorized users can generate or regenerate it. Item details and provider data are loaded on demand.

Browsing an upstream reading does not establish that it has been imported into SanSignal. Use a pipeline and check the resulting instrument history to verify ingestion.

Create a project pipeline

1. Open Ingestion → Pipelines and add an Affinity pipeline.
2. Select the granted Affinity site and destination SanSignal site.
3. Generate the catalog preview.
4. Inspect discovered instruments, channels, profiles, logger proposals, and resulting SanSignal resources.
5. Select supported items to map, review any proposed use of existing resources, and apply the catalog changes.
6. Confirm the pipeline’s live-capture and processing state, then verify a known reading in the instrument view.

Catalog support is specific to the discovered profile. Review unsupported or unresolved entries instead of assuming every item in the upstream inventory will import. Existing logger adoption and relationship changes are explicit choices in the review workflow.

Maintain mappings

The catalog shows provider inventory alongside its resulting SanSignal resources. Use it to inspect a full entry, map or unmap selected instruments, and assign supported catalog selections to groups.

Generate a fresh catalog preview when provider configuration changes. Review the proposed changes before applying them. Unmapping or changing a relationship can affect future data handling, so check the displayed impact.

Live capture and processing

Lifecycle, live capture, and processing are separate controls. Pausing processing does not stop durable capture. Readings can continue accumulating while processing is paused, subject to available capacity and connection state.

Use the activity timeline, health details, and Action required incidents to understand backlog, quarantine, and possible gaps. Do not infer complete data coverage from the connection’s overall status alone.

Historical imports and recovery

Backfill uses available REST history for supported mapped profiles. Select the requested range where offered and inspect the resulting backfill details and progress. Some profiles may support live readings without a historical import contract.

Quarantined or recovery messages need their reported cause resolved before retry. Use Try messages again when appropriate. Discard operations remove retained work and can create unrecoverable gaps where upstream history is unavailable; review the exact affected scope before confirming a discard.

After recovery, compare source timestamps and instrument readings across the affected period. See Runs and troubleshooting for a shared diagnostic workflow.