Install agents

Set up the Flux grid: the hub that owns the repository, XPLG instances as agents at the sources, the Remote account that connects them over HTTPS, proxy instances for isolated segments, and the Windows agent for Windows sources.

What you will do: install a Flux agent next to the data, connect it to the hub with a verified account, and reach agents the hub cannot see through a proxy instance.

A Flux grid has one hub — the XPLG instance or cluster that runs the sync tasks and owns the repository — and agents at the sources. An agent is an ordinary XPLG installation registered on the hub as a Remote XpoLog account and reached over HTTP/S. The wiki recommends Agent Mode — a thin instance that stores no data — for collection-only agents; whether a Flux-only agent should also run in Agent Mode is not stated and is pending confirmation from XPLG engineering. The hub never needs credentials to the sources; the agent holds them. The install is the same as any XPLG server, so follow Deploy for the host, then this page.

Steps: one agent

  1. Install XPLG on a host that can read the sources (same operating system rules as the product: a Linux hub cannot read Windows shares, a Windows agent can).
  2. Switch it to Agent Mode when the instance only collects and forwards (see above): PortX > Settings > System Settings > Activate Agent Mode, Save; the instance restarts, some functions are disabled and every log shows size 0 because nothing is stored.
  3. Add the sources on the agent as you would on any instance (PortX > Data > Add Data): the agent only checks for fresh data and ships it.
  4. Create the account on the hub: PortX > Data > Account > New Account > Remote XpoLog — name (case-sensitive, used in the task XML), host, HTTP or HTTPS, URL context (logeye), port (30303 or 30443), the agent's user and password when its security is on, Enabled. Account type Agent (the hub collects), not Proxy (queries run remotely). Under Advanced Settings tick Enable remote configuration synchronization so every log on the agent appears on the hub; Compress Traffic is on by default.
  5. Verify — a green message confirms connectivity; otherwise check the details and the HTTPS port on the agent.
  6. Reference the account in the task: <Account classKey="xpolog.eye.media.remote.RemoteXplgAccount" name="<account>"/>; see Sync task reference.

The agent typically receives a more limited license; ask XPLG for it.

Isolated segments: proxy instances

When the hub cannot reach an agent, place a Flux instance where it can reach both and declare it in the task as a proxy. The hub talks only to the proxies, the proxies to the agents, over HTTPS:

<ProxyRemote>
  <Account classKey="xpolog.eye.media.remote.RemoteXplgAccount" name="flux-proxy-1"/>
  <Account classKey="xpolog.eye.media.remote.RemoteXplgAccount" name="flux-proxy-2"/>
</ProxyRemote>

Outside any <SyncLogsNode> the proxies apply to every node; inside one node they apply to that node only, so one task can mix direct and proxied agents.

Network and trust

  • Hub to agent, and hub to proxy to agent, is HTTPS on the agent's port; open it in that direction only.
  • Use the customer's certificates on every instance; see Security and integrity.
  • The same Remote XpoLog account type also serves PortX collection (an Agent Mode instance forwarding Windows events) and query proxies; one agent can play both roles.

Checks

  • Verify on the account is green from the hub, and from each proxy to its agents.
  • The agent's logs appear under the hub's Folders and Logs after synchronization.
  • The first task run writes event.data-sync.start and event.data-sync.end for the node in metricevent.log.

Next: Sync task reference

Source: XPLG wiki, pages 2054684673, 1594132790, 2199191556, 2198994949, 2199027716, 2353528833, 1594132401, 1594131316 (https://xpolog.atlassian.net/wiki/spaces/XPOL/pages/2054684673).