alpacon
Monitoring

Monitoring

Alpacon’s Monitoring service collects and displays activity data generated by users within a Workspace.
This allows administrators and users to audit sessions, command executions, and server-side system logs in a centralized and structured way.

The following types of monitoring data are available:


Websh History

The Websh History feature allows you to track when users accessed servers using Websh, and review actions performed during each session.

▸ How to Access

From within a Workspace, go to Audits > Websh History.

▸ Provided Information

FieldDescription
ServerServer name connected via Websh
UsernameAccount used for the session
GroupnameUser's group name
DurationSession duration
OperatorReal name of the user
BrowserBrowser used for access
Remote IPUser’s IP address
TimeSession start time

Click the Details link in each row to view the full session details.

▸ Session Details

The detail page includes:

  • Full connection metadata (server, user, time, etc.)
  • A Record section that lists all terminal commands executed by the user during the Websh session
    → This enables full auditability of user activity.

Command History

The Command History feature displays all shell commands submitted to registered servers via Alpacon, including scheduled and system-internal commands.

▸ Command Types

  • system: User-submitted commands
  • internal: Commands executed automatically by the Alpamon agent

▸ How to Access

From within a Workspace, go to Audits > Command History.

▸ Provided Information

FieldDescription
ServerTarget server name
ShellCommand type (system or internal)
LineExecuted command line
ResultOutput or return message
OperatorUser who submitted the command
StatusCommand state: Sent, Scheduled, Success, Failed
RequestedCommand submission timestamp

Click the expand icon in each row to view detailed execution logs and response metadata.


System Logs

The System Logs feature aggregates log entries generated from user-registered servers,
providing a centralized view of system events, errors, and status reports.

▸ How to Access

From within a Workspace, go to the System Logs menu.

▸ Provided Information

FieldDescription
ServerServer from which the log originated
ProgramProcess or application that generated the log
LevelLog severity (info, warn, error, etc.)
PIDProcess ID
MessageLog content
DateLog timestamp

Click the expand icon to view the full log message and related metadata.