Collector Manager Dashboard Guide

The Collector Manager web UI is a Blazor-based dashboard that runs at http://<host>:8080. It is the primary interface for managing your on-premise security collector agents.

Accessing the Dashboard

1. Open a browser and navigate to http://<host>:8080 (replace <host> with the hostname or IP address of the machine running the Collector Manager container).
2. You will be redirected to the login page at /account/login.
3. Enter your username and password, then click Log in.

Tip

Bookmark the dashboard URL for easy access. After login you are redirected back to the page you originally requested.

Logging In

The dashboard uses cookie-based sessions for the Blazor UI.

• Sessions persist across browser restarts until you explicitly log out.
• Multi-factor authentication (MFA) via a TOTP authenticator app (Google Authenticator, Authy, etc.) is supported and can be enabled per account.
• If you are locked out because you have lost access to your authenticator, an administrator must reset MFA from the command line. Contact support if you need assistance with this.

Navigation

The sidebar contains the primary navigation:

• Activations — lists all registered collector agents. This is the main working area of the dashboard.
• Username link (bottom of sidebar) — opens the account management page for the currently logged-in user.
• Log out button — ends the current session.

Managing Your Account

Click your username in the sidebar to reach the account management page at /account/manage. From this page you can:

• Change your password
• Enable or disable two-factor authentication
• Set up a TOTP authenticator
• Generate MFA recovery codes

Store recovery codes securely

Recovery codes are the only way to access your account if you lose your authenticator device. Store them in a password manager or other secure location. If you lose access to both your authenticator and your recovery codes, contact an administrator to reset MFA from the command line.

Real-Time Updates

The dashboard maintains a persistent SignalR connection to the backend. Container state changes — such as a collector moving from Running to Exited — are reflected in the UI within seconds without requiring a page refresh.

If the connection is lost (for example, because the container restarted), the Blazor circuit will attempt to reconnect automatically.

Notifications

Operations that complete asynchronously — activation, container start/stop, errors, and upgrade results — appear as toast notifications in the corner of the screen. Each notification shows a title, message, and timestamp. Notifications are ephemeral and do not persist across page reloads.