Skip to main content

​
Runtime overview

Beacon supports Factory Droid through an OTLP HTTP launch environment, optional hook telemetry, and a local session-store sync for historical sessions.

​
Prerequisites

Before enabling Factory Droid telemetry, make sure:
  • Factory Droid is installed and available as the droid executable for the user or managed endpoint.
  • beacon endpoint install has run so the local collector, shared endpoint config, and runtime log paths exist.
  • Droid’s launch environment sets OTEL_TELEMETRY_ENDPOINT=http://127.0.0.1:4318 through MDM or another customer-owned policy.
  • Optional hook telemetry is installed with beacon endpoint hooks install --harness factory.
  • Historical session telemetry can be synced from Factory’s local session store with beacon endpoint factory sync.
  • Factory Droid is restarted after launch-environment or hook changes so new sessions use the updated settings.

​
Collection path

Factory Droid can send OTLP HTTP telemetry to Beacon’s local collector. Factory hooks can also invoke Beacon’s hook adapter for richer runtime events where Factory exposes hook payloads. Beacon can also read committed Factory session records from ~/.factory/sessions and convert them into endpoint events marked harness.collection_method=poll.

​
Discovery and status

Beacon detects Factory Droid through the droid executable and validates OTEL_TELEMETRY_ENDPOINT in the effective launch environment. Use beacon endpoint discover, beacon endpoint status, or beacon endpoint hooks status --harness factory to inspect Factory Droid support. Use beacon endpoint factory status to inspect local Factory sessions and how much Beacon has synced.

​
Install or configuration support

beacon endpoint install prepares the collector, shared endpoint config, and runtime log paths. Factory Droid’s launch environment is managed by MDM or customer policy. Install optional Factory hooks separately:
Install optional Factory hooks separately
--harness droid is also accepted for Factory Droid hook installs. Sync Factory’s local session store separately:
Sync Factory session telemetry
For scheduled collection, run beacon endpoint factory sync --watch, or run one-shot sync from your scheduler. --print maps events without writing the runtime log or advancing the cursor.

​
Telemetry coverage

​
Deployment notes

Factory Droid OTLP is controlled by Droid’s launch environment. Set OTEL_TELEMETRY_ENDPOINT=http://127.0.0.1:4318 through MDM or another customer-owned launch policy. Beacon discovers Droid and validates the endpoint, but it does not mutate shell profiles for Droid. Restart Factory Droid after installing or removing hooks so new sessions pick up the updated hook configuration.

Supported agent harnesses

Return to the runtime support overview.

Hooks

Install, inspect, and uninstall runtime hook integrations.