Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.asymptotelabs.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Dashboard Testing

The Beacon endpoint dashboard is a local-only, read-only UI for inspecting the runtime JSONL log. Use it after health checks and validation events to confirm that local events are visible to an analyst.

​
Open the dashboard

Start the dashboard and open it in your browser: 
beacon endpoint dashboard --open
By default, the dashboard binds to a loopback address and reads the configured runtime log plus its numbered local archives. It is intended for local investigation, not remote administration. To use a custom local address: 
beacon endpoint dashboard --addr 127.0.0.1:8765
To inspect a specific runtime log: 
beacon endpoint dashboard --log-path /path/to/runtime.jsonl
Write a validation event, then open Log Search and confirm the event appears in the table. 
beacon endpoint test-event
beacon endpoint dashboard --open
Use filters and quick filters to narrow the view by harness, model, severity, category, failures, approvals, MCP activity, file changes, commands, or events that may need review. Event details should open for rows from either the active log or a rotated archive.
Beacon endpoint Log Search view showing investigation filters, quick filters, event rows, and model-aware search controls.

​
Test Security Overview

Open Security Overview after writing test events or generating local agent activity. Confirm the summary cards and inventory panels reflect the local runtime log you are testing.
Beacon endpoint Security Overview showing security posture metrics, top harnesses, top models, top repositories, MCP servers, and runtime inventory.
Security Overview is useful for confirming event totals, needs-review counts, high or critical activity, denied or blocked activity, failed tools, sessions, top harnesses, top models, top repositories, MCP servers, and runtime inventory.

​
Troubleshooting

If the dashboard opens but does not show expected events, check:
  • The runtime log path shown by beacon endpoint status.
  • Whether the validation event was written with beacon endpoint test-event.
  • Whether you are testing user mode or system mode.
  • Whether --log-path points at the same file you validated.
  • Whether the expected event is in the active log or one of the numbered archives next to it.

beacon endpoint dashboard

Review all dashboard flags and command examples.

Validation events

Write a synthetic event before testing dashboard visibility.

Health checks

Confirm endpoint readiness before opening the dashboard.

Local logs

Confirm the dashboard is reading the intended runtime JSONL log.