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

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.

Setup 1 of 5 · Screenshot placeholder

Open the ScrinOps workspace

Show ScrinOps selected in navigation with Setup, Incidents, and Runs visible.

Future capture briefUse a synthetic account. Hide organization, tenant, user, project, workspace, and URL identifiers.

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.

Setup 2 of 5 · Screenshot placeholder

Choose existing project scope

Show synthetic Project, Workspace, Cloud connection, optional Git, and optional Jira or work selections.

Future capture briefHide real names, provider account or subscription IDs, repository names, work-project keys, connection IDs, and owner data.

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.

Setup 3 of 5 · Screenshot placeholder

Check read-only connection health

Show a synthetic healthy, degraded, or revoked result with the selected scope retained.

Future capture briefHide connection identifiers, account/subscription IDs, tenant IDs, role details, tokens, request IDs, and internal endpoints.

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.

Setup 4 of 5 · Screenshot placeholder

Review readable monitoring sources

Show synthetic AWS or Azure sources with readable and denied states.

Future capture briefReplace source names and regions. Hide log groups, workspace IDs, application names, resource IDs, permission details, and provider payloads.

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.

Setup 5 of 5 · Screenshot placeholder

Confirm the mutation-free preview

Show synthetic Would create, Would preserve, ready or blocked status, and Mutations performed: 0.

Future capture briefHide binding names, infrastructure identifiers, provider scope, queues, storage, audit resources, and customer integration details.

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

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

• 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.