Sources

What you will do: pick the source type that matches how your data is produced and configure it.

Syslog

Network devices, appliances and hosts that send syslog. PortX listens on a port per protocol and parses the standard syslog header; the message body is parsed by the AI-driven parser or a chosen pattern.

Protocols: UDP, TCP, TLS
Ports:     <placeholder>

Use TLS where the network is shared. For remote sites, point devices at a gateway and let the gateway forward to PortX.

HTTPS

Applications, agents and services that post events to an endpoint. Create an endpoint, choose the authentication method and the expected body format (JSON lines, arrays, raw text).

Endpoint:        https://<placeholder-host>:<placeholder-port>/<placeholder-path>
Authentication:  <placeholder>

Kafka

PortX consumes from topics in a consumer group. Configure brokers, the topic list, the consumer group and authentication. Offsets are committed as events are accepted into the persistent queue, so a PortX restart does not lose or duplicate data beyond the configured window.

Brokers:         <placeholder>
Authentication:  <placeholder>

Kubernetes and OpenShift

Collection runs inside the cluster and picks up pod logs and cluster events, tagged with namespace, pod, container and labels. Enable it when installing with Helm or add it to an existing cluster:

Collector install: <placeholder>

SaaS and cloud APIs

Connectors pull from cloud providers and SaaS platforms on a schedule using API credentials with read scopes. Each connector has its own page in the console listing the credentials and the data sets it collects.

Available connectors: <placeholder>

Choosing between push and pull

Push sources (syslog, HTTPS, Kubernetes) deliver data as it happens. Pull sources (Kafka, SaaS and cloud APIs) are fetched by PortX; set the interval to match how fresh the data must be and how much the provider's API allows.

Next: Destinations

Verify with XPLG engineering before publishing.