Access guard
A service in the Stout container on a box. It stands in front of the Lager service on the box and turns away people who do not have access to the box. Stout turns it on when it installs itself on a box. See Security and access.Audit log
A record of actions in your organization: who acted, what they did, and when. Owners and admins read it at Settings > Audit Log. See Audit log and notifications.Box
A Linux machine that runs Lager and controls the instruments that connect to it. After you install Stout on a box, the box also runs the Stout container. The Lager docs call a box a Lager Box.Box access
The right to use a box. An owner or admin assigns each box to a member directly. Owners and admins can see and manage every box in the organization.Box group
A named set of boxes, with a color. A group helps you find and sort boxes. A group does not give anyone access to its boxes.Box lock
A mark on a box that shows that one person uses it. The lock holds that person’s display name, with dots in place of spaces. The Lager CLI takes and reads the same locks. See Locks.CI key
An API key that your CI system uses to send test results to CI Metrics. A CI key works only with the CI Metrics endpoints.Control plane
The Stout service that runs the dashboard and the API. Each box connects to the control plane, and the control plane sends commands and settings to the box. On the Stout hosted service, its addresses are app.stoutdata.ai and api.stoutdata.ai.Display name
The name that Stout shows for you. A display name must be unique in an organization. Stout uses your display name as the holder of each box lock that you take.Factory suite
A set of Python files that Factory runs as an ordered list of test steps. Each step passes or fails, and an operator can answer prompts during a run. See Factory.Feature access
A setting that controls which Stout features a member sees in the dashboard. An owner or admin turns each feature on for all members or for selected members.Heartbeat
A short status message that the Stout container on a box sends to the control plane every 30 seconds. If no heartbeat arrives for 3 minutes, Stout marks the box as offline.Invitation
A link that adds a person to an organization. An owner or admin creates it. The link is valid for 7 days, and it works one time.Net
A name for one physical connection to an instrument channel on a box, for examplesupply1. A test script uses the net name, so the script still works when an instrument moves to a different port.
This concept comes from Lager, the open-source
runtime that Stout sits on top of. For the full reference, see the Lager
documentation.
Organization
The top level in Stout. Every box, suite, variable, and membership belongs to one organization. One person can belong to more than one organization.Role
The set of permissions that a person has in an organization: Owner, Admin, or Member. See Roles and permissions.Select Test
A Workbench page that runs a Python test from your GitHub repository on a box. See Select Test.SSH lockdown
A set of SSH settings that Stout applies to a box after it installs itself. Password sign-in and root sign-in stop. Only the SSH keys that Stout installs on the box can sign in.SSO
Single sign-on. People in your organization sign in to Stout through your OIDC identity provider. See Single sign-on.Stout container
A Docker container namedstout that Stout installs on each box, next to the Lager container. It sends heartbeats to the control plane, runs the access guard, and serves webcam streams.