Manage how shop-floor endpoint agents authenticate to this server, build the agent for this site, and set what it reports and how often.
The endpoint agent reports with a single managed key scoped to endpoint telemetry only. It is separate from every other collector, so rotating or revoking it stops all endpoint-agent traffic immediately without touching the PC or GE-Enforce collectors.
Active key {{ key.tokenprefix }}...,
created {{ formatDate(key.createddate) }}.
Last used {{ formatDate(key.lastusedat) }}.
Not used yet.
No endpoint agent key is active. Generate one to let agents report with a managed credential.
On. The bootstrap COLLECTOR_API_KEY still authorizes endpoint reports. Generating a key turns this off so the managed key becomes the only credential. Off. Only the managed key above authorizes endpoint reports, so revoking it is an instant kill switch.
It will not be shown again. Configure it as the agent
X-API-Key header value.
{{ secret }}
.env fallback so
the managed key becomes the only accepted credential. The full
secret is shown once - store it in the agent config as the
X-API-Key header.
Produce an instance-locked agent executable stamped with this server's URL, the endpoint agent key, and the reporting cadence, so it deploys with no manual configuration on the client.
Coming soon. The build pipeline is not wired up yet -
the C# agent runtime is still under development. Generate a key above
and configure it manually as the agent X-API-Key for now.
Define what the agent collects and how often: reporting cadence, monitored processes and services, the curated Windows event list, and whether unknown hosts self-adopt on first contact. These settings are stamped into the build above so a deployed agent needs no local edits.
Coming soon. These controls arrive with the C# agent runtime. Until then the agent uses its built-in defaults.