Commands
Every command sent to a registered server through Alpacon — including the ones the Alpamon agent runs automatically — leaves a record here. Use this page to confirm a command ran, see who triggered it, and read what came back.
How to get here
Open the sidebar and go to Audit → Events → Commands (or My events → Commands if you’re a regular user).
What’s in the list
| Column | What it shows |
|---|---|
| Server | The server the command targeted |
| Shell | Where the command came from: system (user-submitted) or internal (Alpamon agent task) |
| Line | The command line that was executed |
| Result | The output or return message |
| Operator | The user (or token) that submitted the command |
| Status | The current state of the command — running, scheduled, finished successfully, failed, or unresponsive |
| Delay(s) | Seconds the command waited before the server picked it up |
| Elapsed(s) | Seconds the command took to run |
| Date | When the command was submitted |
Click the expand icon on any row to see the full execution log and the response metadata.
What the statuses mean
- Scheduled — the command is queued and waiting for the server to be ready.
- Running — the server has picked the command up and is executing it now.
- Success — the command finished without error. The Result column shows the output.
- Failed — the command finished but returned an error. The Result column shows the error message.
- Unresponsive — the command has been running too long without sending an update back. Usually needs investigation.
Who sees what
The page is open to all users, but the rows scope to your role.
Regular users see only the commands they themselves issued. The sidebar label is My commands.
Administrators see every command across the workspace. The sidebar label is Commands.
The narrowing is enforced server-side — direct URLs follow the same rule.
Common things you’d check here
- Operations — confirm a scheduled command actually ran. Track automated agent tasks and deployment commands.
- Debugging — open a failed command to read the error message and trace what went wrong.
- Security — review privileged or unusual commands. Spot commands no one should have submitted.
- Personal review — look up your own past commands to recover an answer or copy the line.