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.

​
Jamf Deployment

Jamf Pro can deploy and inventory the local Beacon endpoint agent on managed Macs. Beacon’s Jamf support is deployment-native: Jamf installs the package and reports endpoint health while Beacon writes telemetry to local JSONL without requiring a hosted account or Jamf Pro API credentials.

​
What Jamf manages

SignalHow it helps
Package installationDeploy Beacon binaries, endpoint scripts, Jamf helpers, and extension attributes.
System endpoint configurationInstall launchd service files and collector configuration for system-mode telemetry.
Runtime telemetry locationWrite endpoint events to /var/log/beacon-agent/runtime.jsonl.
Inventory and remediationUse extension attributes and Smart Groups to identify missing, stale, or unhealthy installs.

​
Deploy with Jamf

Build or obtain a signed Beacon macOS package, upload it to Jamf Pro, and attach the package to a policy that runs Beacon’s Jamf install helper.
1

Upload the Beacon package

Upload the signed Beacon macOS package to Jamf Pro. The package installs Beacon binaries under /opt/beacon and includes Jamf helper scripts and extension attributes.
2

Create an install policy

Create a Jamf policy that installs the Beacon package and runs the install helper:
/opt/beacon/jamf/scripts/install.sh "$@"
3

Configure policy parameters

Set Jamf script parameters when you need to override the defaults:
ParameterValue
4Harnesses, default claude,codex.
5Content retention, default metadata.
6OTLP gRPC port, default 4317.
7OTLP HTTP port, default 4318.
8Collector path, default /opt/beacon/bin/beacon-otelcol.
9No-start flag, accepts 1, true, or yes.
4

Validate the deployment

After the policy runs, validate the endpoint state on a managed Mac:
sudo /opt/beacon/bin/beacon endpoint status --json
sudo /opt/beacon/bin/beacon endpoint wazuh validate
sudo launchctl print system/com.beacon.endpoint.collector

​
Inventory with extension attributes

Upload the scripts from /opt/beacon/jamf/extension-attributes to Jamf Pro to inventory:
  • Beacon version
  • Collector service health
  • Last runtime event age in seconds
  • Content retention mode
  • Configured harnesses
  • Runtime log writability
Suggested Smart Groups:
  • Beacon version is not_installed.
  • Collector service health is not running.
  • Last runtime event age is greater than 86400.
  • Content retention is not metadata.
  • Runtime log writability is not writable or creatable.

​
Troubleshooting

If the Beacon version extension attribute reports not_installed, confirm the Jamf policy installed the Beacon package before running /opt/beacon/jamf/scripts/install.sh.On the device, verify that the expected files exist:
ls /opt/beacon/bin/beacon
ls /opt/beacon/jamf/scripts/install.sh
Re-run the install policy after confirming the package is scoped to the device.
Check the endpoint status and launchd service state:
sudo /opt/beacon/bin/beacon endpoint status --json
sudo launchctl print system/com.beacon.endpoint.collector
If the service file or collector configuration drifted, run /opt/beacon/jamf/scripts/repair.sh from a Jamf remediation policy.
Verify that the runtime log exists and is writable:
sudo test -w /var/log/beacon-agent/runtime.jsonl
sudo /opt/beacon/bin/beacon endpoint wazuh validate
If validation succeeds but events remain stale, confirm the configured harnesses match the AI runtimes installed on the device and that the local collector ports are not in use by another process.
Check Jamf parameter 4 on the install policy. The default is claude,codex; set the parameter explicitly when you want a narrower or broader harness list.After changing the policy, run the repair script so Beacon reapplies harness telemetry configuration without removing runtime logs.
Check Jamf parameter 5 on the install policy. The default is metadata, with redacted and full available when approved for your deployment.Use the content retention extension attribute to verify the deployed mode across managed Macs.

​
Repair and uninstall

Use /opt/beacon/jamf/scripts/repair.sh as a remediation policy for Macs where extension attributes report a stale or unhealthy install. Use /opt/beacon/jamf/scripts/uninstall.sh to remove endpoint service files. Set BEACON_KEEP_LOGS=1 or Jamf parameter 4 to preserve runtime logs during removal. Set BEACON_KEEP_CONFIG=1 or Jamf parameter 5 to preserve harness telemetry configuration.