Skip to content
ScrinCloudScrinCloud Docs

Availability and setup

ScrinOps setup reuses existing ScrinCloud references. The page never asks for cloud credentials and does not copy project, workspace, connection, Git, work-management, or billing ownership records.

Typical time
10–20 minutes
You need
An enabled ScrinOps environment and existing cloud connection
Outcome
A read-only readiness preview

Step 1: Open ScrinOps

Section titled “Step 1: Open ScrinOps”

From the authenticated workspace navigation, open ScrinOps. The workspace contains Setup, Incidents, and Runs.

If ScrinOps is missing, the deployed frontend capability is disabled. Do not assume a manually entered route enables the underlying APIs.

ScrinOps workspace with Setup selected and the Incidents and Runs sections visible.
Setup 1 of 5 · Open the ScrinOps workspaceSynthetic ScrinOps workspace with Setup, Incidents, and Runs visible.

Step 2: Select Existing Core scope

Section titled “Step 2: Select Existing Core scope”

In 1. Existing Core scope, select:

  1. Project;
  2. Workspace;
  3. Cloud connection;
  4. optional Git context; and
  5. optional Jira / work context.

Project, workspace, and cloud connection are required for the preview actions. Changing the project or cloud connection clears earlier results so stale readiness is not carried into a new scope.

Synthetic existing Core scope form with project, workspace, cloud connection, optional Git, and optional work selections.
Setup 2 of 5 · Choose existing project scopeSynthetic Project, Workspace, Cloud connection, optional Git, and optional work selections.

Step 3: Check health

Section titled “Step 3: Check health”

Choose Check health in 2. Connection health and source discovery. The result is healthy, degraded, or revoked.

The check uses short-lived server-side access. Do not enter access keys, client secrets, tokens, passwords, role credentials, or provider exports into the browser or a support message.

Synthetic ScrinOps connection-health panel showing a healthy read-only result.
Setup 3 of 5 · Check read-only connection healthSynthetic healthy connection result with the selected scope retained.

Step 4: Discover readable sources

Section titled “Step 4: Discover readable sources”

Choose Discover sources. Review Readable observability sources and the source kind and region. A denied source remains disabled. Turning a source toggle on or off only changes the current preview selection; it does not change the provider resource.

Supported visible source kinds include alarms, metrics, log groups, Log Analytics, and Application Insights, depending on provider access.

Synthetic ScrinOps source discovery with readable alarm and log-group entries plus a denied metric entry.
Setup 4 of 5 · Review readable monitoring sourcesSynthetic provider-neutral sources with readable and denied states.

Step 5: Run dry preview

Section titled “Step 5: Run dry preview”

In 3. Mutation-free dry run, choose Run dry preview. Review:

  • Would create and the overall ready or blocked status;
  • Would preserve during teardown;
  • selected source count and optional integration state; and
  • Mutations performed: 0.
Synthetic ScrinOps mutation-free preview showing ready create and preserve summaries with zero mutations performed.
Setup 5 of 5 · Confirm the mutation-free previewSynthetic ready preview with Would create, Would preserve, and zero mutations.

What this page does not do

Section titled “What this page does not do”

The Setup page does not expose an activation or enable action. A healthy check, discovery response, or ready dry preview does not prove that alert intake, evidence collection, or incident correlation is deployed and running.

Check your result

Section titled “Check your result”

The intended project, workspace, and cloud connection remain selected; health and source results belong to that scope; and the dry preview reports zero mutations.

Common blockers

Section titled “Common blockers”
  • No project options: create or gain access to an existing project first.
  • No workspace: the selected project needs an accessible workspace.
  • No cloud connection: connect and activate a supported provider account.
  • Degraded or revoked: repair the existing connection before retrying.
  • No sources: check provider permissions, selected scope, and reporting region.
  • Request unavailable: the deployed ScrinOps control-plane contract may not be enabled for this environment; the preview did not change infrastructure.