Skip to main content
Live monitoring is the day-two operations surface for RADIUS. Use it to see whether authentication is working, isolate failures, inspect sessions, and jump from a log entry to the affected user or NAS device.

​
Prerequisites

Before you use Live View effectively, confirm that:
  • At least one NAS device is sending authentication traffic.
  • Users and groups exist for the traffic you expect to see.
  • You know the approximate time range for the issue or test.
  • You have permission to view logs and entity dashboards.

​
Live View

Open Live View from the RADIUS navigation. The page combines metrics and a full log table, with filters for common operational questions. Use Live View to answer:
  • Are authentications succeeding?
  • Which users are being rejected?
  • Which NAS device is sending bad or unexpected traffic?
  • Are failures concentrated in one folder, device, or timeframe?
  • Are suspended users attempting to authenticate?
  • Are requests missing attributes or other required information?

​
Filters

The log card supports:
  • Status type filters.
  • Failures-only toggle.
  • User filter.
  • Folder filter.
  • Device filter.
  • Timeframe filter.
  • Search by log ID.
  • Sort field and sort direction.
  • Refresh.
The global RADIUS filter model supports timeframes including 1 hour, 3 hours, 6 hours, 12 hours, 24 hours, and 7 days. User dashboards also include user-focused ranges such as last 24 hours, last 7 days, and last 30 days.

​
Status Categories

The monitoring UI groups authentication outcomes into practical categories:
CategoryWhat it means
SuccessSuccessful authentications and authorizations.
MissingUsers missing required attributes or information.
Bad PasswordUsers who attempted to log in with incorrect credentials.
RejectedUsers rejected during the authentication process.
SuspendedUsers blocked from accessing the network.
The raw RADIUS message types available in filters include Access-Accept, Access-Reject, and Access-Challenge.

​
Accounting Metrics

When accounting is enabled on the NAS, Altostrat can use accounting data for sessions, usage, quotas, and dashboards. The RadSec edge publishes accounting data asynchronously so the NAS receives an Accounting-Response without waiting on the metrics pipeline. The monitoring pipeline tracks:
  • Input and output bytes, including Gigawords for 64-bit counters.
  • Input and output packets.
  • Session duration.
  • Accounting packet count.
  • Session start time.
  • Session stop time.
  • Last framed IP address.
  • Accounting status type such as Start, Stop, Interim-Update, Accounting-On, and Accounting-Off.
Authentication results are also counted with labels for workspace, organization, NAS, username, and reject reason when available. The accounting path and authentication path are intentionally separate. Accounting and post-authentication events stream into the analytics plane after packets are handled, while authentication outcomes and NAS logs are produced by the RADIUS service and background metrics jobs. This keeps live packet handling responsive while still giving operators a joined view in the UI. Authentication logs and accounting data are retained for 12 months. For capacity and retention planning, see Limits and Availability.

​
Accounting Triggers

Accounting triggers let you automate follow-up actions from usage data, such as acting when a user exceeds a monthly data threshold. Use them when an operational response should be driven by accounting events rather than by a manual dashboard review. Triggers depend on reliable accounting. Configure Start, Stop, and Interim-Update packets on the NAS, and keep interim update frequency at or above the supported minimum interval documented in Limits and Availability.

​
Admin Request Metrics

CoA and PoD events are tracked as admin request activity when dynamic authorization packets are sent or observed by the platform. Use this with NAS logs and device-side logs when you are validating manual disconnects, quota-triggered disconnects, or CoA behavior.

​
Log Table

Expanded logs show:
  • Status or reply message.
  • Execution time in milliseconds.
  • User, with a link to the user detail page when available.
  • Device, with a link to the NAS detail page when available.
  • Folder or container when present.
  • IP address when present.
  • Timestamp.
Click a log row to inspect the request and response details. Use the user and device links to continue the investigation from the most relevant entity dashboard.

​
User Dashboard

The user detail page is the best place to investigate one account. It includes:
  • Time range selector.
  • Usage and session charts where data is available.
  • Latest session.
  • Active session state.
  • Latest IP address.
  • Group membership.
  • Realm link.
  • Effective check and reply attributes.
  • Logs scoped to the user.
  • Actions for edit, suspend or enable, delete, move, reset credentials, and disconnect session.
Use this page when the same user repeatedly fails, consumes unexpected usage, or needs an active session disconnected.

​
Device Dashboard

The NAS detail page is the best place to investigate one device. It includes:
  • Logs scoped to the NAS.
  • Total requests.
  • Success rate.
  • Active sessions.
  • Reject count.
  • RadSec configuration values.
  • Certificate downloads.
  • CoA and PoD settings.
  • Device metadata.
Use this page when many users behind the same NAS fail at the same time, or when you are validating a new router, access point, VPN gateway, firewall, or wireless controller.

​
Operational Workflow

1

Start broad

Open Live View and set the timeframe around the incident or test.
2

Filter to failures

Turn on failures only, then narrow by status category if needed.
3

Find the entity

Use the log row to identify the user, NAS device, folder, and response.
4

Open the dashboard

Jump to the user or NAS dashboard for scoped logs and related metrics.
5

Change one thing

Fix the credential, status, group, realm, NAS setting, or attribute issue you found.
6

Retest

Authenticate again and confirm the new log entry has the expected outcome.