Operation history and application observations

Qualified private pilot, reviewed 22 September 2026. This feature covers the server scalar-offset workflow and the OAuth QGIS scalar-map connector. It does not record every action inside QGIS, ResInsight or other applications.

Inspect a calculation

1. Open a supported scalar asset in Workspace or the QGIS connector.
2. Run a server offset and wait for publication of the new revision.
3. Open the project’s Activity page. Inspect the completed operation’s exact input/output revisions, parameters, lineage and operation ID.
4. Use Download loaded events (JSONL) to take a readable copy. This button exports only the events loaded by the page (up to 500). Use the paginated API and export utility for complete history.

The operation’s scientific meaning stays attached to the exact snapshot. For an offset, units and missing values are preserved and coordinates do not move. This is not a CRS transformation. Older operations are not backfilled into Activity. The native project service remains authoritative; this feature does not move data into OSDU or create an additional scientific authority.

Understand connected applications

After restarting QGIS with connector 0.4.0, sign in through Browse Workspace and add a scalar asset. Its applied revision and follow/pin/copy mode appear in Activity. These are client-reported observations. They establish what the connector reports applying, not that a person viewed or approved the result.

A recent report does not guarantee the client is still online. A detached copy reports once and does not follow revisions. Paused or disconnected clients may show “not seen recently.” Legacy connection-file clients do not automatically report. New reports separate notification waiting, download, preparation and GUI layer application. Historical inclusive durations remain labelled legacy. Neither GUI application nor server publication-to-report lag measures final screen paint.

The coverage section lists what each integration can observe and what it cannot. Our own scalar operator records its parameters and exact inputs. The QGIS connector records its own delivery, but not arbitrary QGIS edit recipes. ResInsight and file profiles are currently declarations without event publishers. Never treat missing evidence as an inferred operation history.

Optional Jaeger diagnostics

Your administrator can enable customer-controlled OpenTelemetry collection and Jaeger. Expand Operation details and related deliveries in the operation’s card. Copy trace ID copies the 32-character diagnostic ID. Do not paste the longer durable operation ID into Jaeger’s trace search. Open in Jaeger appears when IT configures a reachable viewer URL. Its waterfall shows acquisition, worker calculation and publication spans. Separate delivery traces link back to the producing operation; heartbeats do not create duplicate traces. This helps diagnose delays. Trace sampling, export failures and retention may remove diagnostics; they must not remove durable operation history.

There is no automatic vendor analytics destination. Customers control diagnostic endpoints, access and retention. The diagnostic backend has its own permissions; Workspace project access does not automatically secure a separately deployed Jaeger UI or SQL database.

Recovery and export

An unconfirmed publication needs reconciliation. Retry the same command ID through its originating caller; do not assume the operation failed and repeat it as a new command. The native commit and local completion journal are separate transactions. Layer-reporting failures retry independently and do not block map updates. Check the QGIS dock’s observation status.

A customer-run export can write JSONL or PostgreSQL with resumable checkpoints. Unavailable destinations, expired credentials and revoked access stop further export without advancing the checkpoint. Previously exported customer copies remain readable. Interactive API delegates last five minutes and depend on their browser session. Unattended exports can instead use a dedicated, project-scoped OIDC workload identity with renewable credentials; see the API reference.

Administrators can set delivery-observation retention independently of scientific history and Jaeger traces. An exporter encountering pruned observations stops and requires explicit acceptance of the retained history. It cannot recover deleted observations. Scientific operation records are not pruned by this setting.

Portable history is baseline functionality. Managed collection, fleet dashboards, alerts and extended retention may become commercial services. No licence gate on history export is implemented in this pilot.

See the event/API contract and QGIS Workspace connections.