The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu
Go agent-ai-cliagent-harnessesagent-securitybrowser-extensionciclaude-codecloudcodexcursordetection-engineeringjevknowledge-basememorymobile-device-managementobservabilitysecuritysecurity-information-and-event-managementsecurity-toolstelemetrytraces
---
title: "Local JSONL"
description: "Use Beacon's local runtime JSONL log as the default endpoint log and local dashboard source."
---
## Local log output
Beacon's default destination is the local [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log). The endpoint agent writes one normalized [endpoint event](/concepts/core-concepts#endpoint-event) per line and keeps the active path stable for local review, the Beacon dashboard, and downstream shippers.
Use this path when you want a local audit trail without configuring a remote SIEM, log aggregator, or object storage exporter.
## Runtime log paths
| Mode | Runtime log |
|------|-------------|
| User mode | `~/.beacon/endpoint/logs/runtime.jsonl` |
| System mode | `/var/log/beacon-agent/runtime.jsonl` |
User mode is convenient for local evaluation. System mode is preferred for package or MDM deployments because the log path is shared and root-managed.
## What reads the local log
Beacon uses the same JSONL source for:
- Local inspection with `beacon endpoint status`, `beacon endpoint doctor`, and diagnostics commands.
- The loopback-only [endpoint dashboard](/cli/dashboard), including activity sessions, findings, detections, token usage, and inventory.
- Validation events written by forwarding commands.
- Customer-managed shippers that tail the active `runtime.jsonl` path.
Beacon rotates the active log at 10 MiB and keeps five numbered archives such as `runtime.jsonl.1`. The active `runtime.jsonl` path remains the stable handoff point for the local dashboard and external shippers.
### Reading the log on Windows
Rotation renames the log. Windows refuses to rename a file that another process has open, unless that process allowed deletes when it opened the file. Vector allows it. PowerShell's `Get-Content` and `[IO.File]::OpenRead` do not, and if you use another agent, check how it opens files.
If you write your own shipper, open the log with read, write and delete sharing:
```powershell title="Open the log the way rotation needs"
$stream = [System.IO.File]::Open($path, 'Open', 'Read', [System.IO.FileShare]'ReadWrite, Delete')
```
A reader that does not share deletes holds rotation up for as long as it keeps the file open. Beacon keeps appending to `runtime.jsonl` past 10 MiB and rotates once the file is closed, so no events are lost, but the log grows in the meantime. After a rotation, a handle you already hold reads the renamed `runtime.jsonl.1`, so reopen `runtime.jsonl` when you reach the end of the old file.
## Inspect locally
Confirm the endpoint is healthy and writing events:
```bash title="Confirm the endpoint is healthy and writing events"
beacon endpoint status --json
beacon endpoint test-event
```
For a system-mode deployment:
```bash title="For a system-mode deployment"
sudo /opt/beacon/bin/beacon endpoint status --system --json
sudo /opt/beacon/bin/beacon endpoint test-event --system
sudo test -r /var/log/beacon-agent/runtime.jsonl
```
Open the local dashboard:
```bash title="Open the local dashboard"
beacon endpoint dashboard --open
```
## Content handling
Beacon applies redaction, sanitization, truncation, and event-size limits before events are written to local JSONL. Review filesystem access, archive retention, and any downstream readers so retained telemetry matches your approved collection policy.
## Related
<Columns cols={2}>
<Card title="beacon endpoint dashboard" icon="chart-line" href="/cli/dashboard">
Inspect Beacon runtime logs in the local dashboard.
</Card>
<Card title="Log forwarding" icon="tower-broadcast" href="/log-forwarding">
Compare local, SIEM, log aggregation, and object storage paths.
</Card>
<Card title="Customer-managed log pipelines" icon="route" href="/log-forwarding/customer-managed">
Forward local Beacon JSONL through customer-controlled shippers.
</Card>
<Card title="Endpoint event schema" icon="code" href="/telemetry-schema/event-schema">
Review normalized Beacon JSONL fields and example events.
</Card>
</Columns>