Skip to main content

Managing Endpoints via the Portal

The Myrmex Portal is your central command center for deploying agents and monitoring the health of your infrastructure.

Endpoint Registration

The platform offers multiple ways to provision new agents depending on your deployment scale.

1. Register Single Device

Ideal for manual installation on a specific workstation or server.
  • Path: IntegrationsEndpoint ListAdd EndpointRegister Single Device.
  • Process: Fill in the device metadata (Name, Context, OS, Severity), then go to the Command Line tab to copy the installation string.

2. Collector Registration (Guided Flow)

Specifically for setting up the agent in Collector Mode.
  • Path: IntegrationsAdd Collector.
  • Step 1: Provide device identification.
  • Step 2: Execute the generated installation commands.
  • Step 3: Validate Collector to ensure bidirectional connectivity is established.

Authorization & Status

Safety is paramount. Every new agent must be explicitly authorized before it can stream telemetry or execute actions.

Device Cards

In the Endpoint List, each device is represented by a card showing:
  • Hostname & OS: The physical identity of the device.
  • Status (Online/Offline): Determined by continuous heartbeat checks.
  • Authorization: Authorized (Active) or Unauthorized (Pending).

Managing Authorization

If a device appears as Unauthorized:
  1. Open the device’s action menu (three dots).
  2. Select Authorize.
  3. Confirm the device details in the Endpoint Authorization panel.

Operational Control

From the portal, you can trigger remote actions directly on the endpoint agent.
  • Service Control: Start, Stop, or Restart the agent service.
  • Monitoring: Adjust granular monitoring parameters and toggle real-time collection.
  • Inventory Details:
    • Inventory Tab: View host specs, CPU/Memory graphs, and hardware diagnostics.
    • Integrations Tab: See which sub-agents and specialized tools are active on this device.

Status Logic & Timeouts

The portal uses specific intervals to determine device health:
  • Heartbeat Timeout: If an agent doesn’t check in within the AGENT_MAX_OFFLINE_TIME (default 600s), it is marked Offline.
  • Sync Interval: The system refreshes connection states every 60s.
Actions and telemetry require the device to be both Online and Authorized.