DevOps / Guide

How DevOps is operated.

DevOps watches the systems you connect, decides what is wrong, acts only within the authority you grant, verifies the result independently, and keeps the evidence. This guide shows how its operations console is organized and how an incident is worked, so you can see what operating it will involve.

Start the tutorial See every command

At a glance

Where you use it: In an operations console inside the connected system's own administration. There is no customer console yet: the managed service is planned.
Customer path: Admins who watch: status, alerts, logs, evidence, and registered checks.
Admin path: Owners who authorize: approvals, maintenance, and acting on AI advice.
DevOps today: PlannedNot publicly hosted

Tutorial

Operate it step by step.

Follow every step, or only the customer or admin path. Your progress stays in this browser.

Step 1 of 7 · Customer and Admin

Find your way around the console

Know what each part of the operations console is for.

Do this

Status, Alerts: What is healthy and what is not.
Logs, Evidence: What happened, with secrets removed and every decision recorded.
Approvals, Maintenance, AI advice: Owners only: deciding and acting.
Configuration, Version: How the connection is set up.

You should see. A menu that shows each person only the parts their role allows.

Tip. Opening a menu entry never runs anything by itself. Every action goes through its own gate.

Step 2 of 7 · Customer

Check status and alerts

See whether the connected system is healthy, and what needs attention.

Do this

Status: Overall health, then Workflows for each running workflow.
Alerts: Current alerts and how long each has been open.

You should see. A clear picture of what is wrong, if anything.

Step 3 of 7 · Customer

Read the logs and the evidence

Understand an incident from its record.

Do this

Logs: Recent logs, sanitized.
Evidence: The incident's trail: detection, decision, action, and independent verification.

Illustrative example

Bot: Incident example-1 Detected: health check failing Authorized: stale-lock cleanup within policy Verified: health check passing

You should see. Enough to explain what happened and why it is fixed.

Step 4 of 7 · Customer

Run a registered check

Confirm health on demand.

Do this

Tests: Runs a health or smoke check the connected system registered and allows.

You should see. The check's result, added to the evidence.

Step 5 of 7 · Admin

Decide on an approval

Authorize, or refuse, an action DevOps prepared.

Do this

Approvals: Each waiting action, with what it would do and why.
Approve or refuse: Only an owner decides; nothing outside the granted authority runs.

You should see. The action runs within its limits and is verified, or it is recorded as refused.

Step 6 of 7 · Admin

Run maintenance

Run a registered maintenance action, such as a bounded cleanup.

Do this

Maintenance: Lists registered actions; each needs its own approval before it runs.

You should see. The action's outcome and its evidence.

Tip. Patch application, migrations, deployments, and restores are never run from the console.

Step 7 of 7 · Admin

Use AI advice

Get an analysis of an incident and a proposed remedy, without giving AI authority.

Do this

AI advice → Proposals: Checks a proposed remedy against policy.
Remediation handoff: Prepares the remedy as a reviewed change in your repository.
Repository dispatch: Starts an allowlisted workflow, after an owner's separate approval.

You should see. A reviewed change or an approved, verified action. AI advice alone changes nothing.

Command tree

Every command and menu, expanded.

Typed commands, menus, and the buttons inside them, with who can use each. A step link opens the part of the tutorial that walks through it.

Operations console

In the engine, which is in development. The connected system decides which parts to show; nothing here is available to customers yet.

Operations consoleMenuCustomerAdmin
The operator menu a connected system shows its admins and owners. Step 1
- StatusScreenCustomerAdmin
  Health of the connected system at a glance. Step 2
  - WorkflowsScreenCustomerAdmin
    The state of each running workflow. Step 2
- AlertsScreenCustomerAdmin
  What is wrong now, and since when. Step 2
- LogsScreenCustomerAdmin
  Recent logs, with secrets removed. Step 3
- EvidenceScreenCustomerAdmin
  The recorded trail for each incident: what was seen, decided, done, and verified. Step 3
- TestsScreenCustomerAdminNeeds the check to be registered and allowed
  Registered health and smoke checks. Step 4
- ApprovalsScreenAdmin
  Actions waiting for an owner's decision. Step 5
- MaintenanceScreenAdminNeeds an owner's separate approval
  Registered maintenance actions, such as bounded cleanups. Step 6
- AI adviceScreenAdmin
  Advisory analysis of an incident; it proposes, it never acts. Step 7
  - ProposalsScreenAdmin
    Checks a proposed remedy against policy before anyone acts on it. Step 7
  - Remediation handoffScreenAdmin
    Prepares a reviewed change for your own repository. Step 7
  - Repository dispatchScreenAdminNeeds an owner's separate approval
    Starts an allowlisted repository workflow. Step 7
  - FallbackScreenAdminNeeds an owner's separate approval
    A bounded fallback when the repository path is unavailable. Step 7
- ConfigurationScreenCustomerAdmin
  A safe summary of how the connection is configured. Step 1
- VersionScreenCustomerAdmin
  The engine version and its facts. Step 1

Not listed: the engine's internal names and tools, actions it keeps permanently disabled, and ApexAi's own host tooling. DevOps is planned as a managed service; this guide describes how its engine is operated today.

Troubleshooting

When something does not work.

Common DevOps problems and how to fix them
What you see	What to do
A console entry I expect is missing	The connected system decides which parts to show, and each role sees only its own. Owners see Approvals, Maintenance, and AI advice. Find your way around the console
An action will not run	Every action needs its own gate, usually an owner's approval. Opening its menu entry is not enough. Decide on an approval
AI advice did not fix anything	By design: advice proposes and prepares; changes run only through an approved, verified path. Use AI advice

Back to DevOps Discuss DevOps