Collect

Bring telemetry into PortX from syslog, HTTPS, Kafka, Kubernetes and OpenShift, SaaS, cloud and API connectors.

What you will do: connect a first source to PortX and confirm its data arrives as a stream.

PortX collects from anywhere. A source is anything that produces logs, events or metrics; PortX either listens for what the source pushes or pulls from the source's API.

Source types

  • Syslog — devices and hosts that send syslog over UDP, TCP or TLS.
  • HTTPS — applications and agents that post events to a PortX endpoint.
  • Kafka — topics PortX consumes from.
  • Kubernetes and OpenShift — pod logs and cluster events collected inside the cluster.
  • SaaS and cloud APIs — cloud providers and SaaS platforms that PortX pulls from with connectors.

The full list is under Integrations: Sources.

Steps: a first source

  1. In the PortX console, open the sources area and choose Add source:
Console path: <placeholder>
  1. Pick the source type and give the source a name you will recognise in routing policies.
  2. Configure how data arrives: a listening port for syslog or HTTPS, broker and topic for Kafka, cluster credentials for Kubernetes, API credentials for SaaS and cloud connectors.
Default ports: <placeholder>
  1. Save. The source shows a stream once data arrives. Send a test event if the source is quiet.
  2. Open the stream to see parsed events. AI-driven parsing proposes a structure for unknown formats; accept it or adjust the fields.

Agents and gateways

Where PortX cannot reach a source directly — a remote site, a locked-down network, an air-gapped segment — an agent or a proxy/gateway forwards the data to the nearest PortX node. Gateways also let you keep a single egress point per site.

What to check

  • The stream's event rate matches what the source should produce.
  • Timestamps are parsed in the right time zone.
  • Fields you will route or filter on are extracted.

Next: Control and route

Verify with XPLG engineering before publishing.