FAQ

What you will do: get the one-paragraph answer, then follow the link for the full page. Commercial questions (pricing, offers, partners) are on the portal's FAQ.

Deployment

Is XPLG a cloud service? No. XPLG is self-hosted: on premises, in your data centre or in your own cloud account, air-gapped if you need it. XPLG Cloud is a hosted tenant by request only. See Deploy overview.

Which environments are supported? X8 as Docker or Podman Compose on a Linux host; V7 with the installer on RHEL 9+, Ubuntu 20.04–24.04, Windows Server 2016+ (macOS 12+ for evaluation); VM images from the AWS, Azure and Google Cloud marketplaces. Kubernetes, OpenShift, Tanzu, Swarm and the managed container services are planned targets, and today a data source through Fluent Bit. See System requirements.

What do I need for a first try? One Linux host with 16 GB (32 GB recommended), Docker and Compose, and ten minutes: Your first deployment in 10 minutes.

Which ports? 30303 (HTTP) and 30443 (HTTPS) for the console and inter-node traffic; 514 UDP / 1468 TCP for syslog; 2055 for NetFlow; outbound 443 to dock for the heartbeat. X8 roles use 30304–30308. Full tables on System requirements.

V7 or X8? X8 for new Linux deployments and clusters; V7 where Windows collection or a non-container host is required. Both run the same products and accept the same licenses.

Data

How does data get in? Push to a listener (syslog, HTTP/S with a token, Kafka and Event Hubs, NetFlow, SAP) or pull by XPLG (files and UNC, SSH, Windows Events, S3, JDBC, cloud and SaaS plugins). Fluent Bit is the recommended shipper for hosts and clusters. See Sources and Fluent Bit.

Do I need an agent? No XPLG agent; Fluent Bit or syslog on the source, or agentless pull with read permission.

Where does the data go afterwards? Forwarders deliver over HTTP/S, Kafka, file, syslog, to another XPLG instance or a socket, with flows that filter, transform (JSON, CSV, CEF, LEEF) and mask. See Destinations.

How long is data kept? As long as the Collection Policy says: hot retention on the index, then a compressed archive (about 90 %) locally or on S3 with checksums. There are no product-imposed retention limits.

Licensing

How is XPLG licensed? One license per server or cluster, bound to the server key generated in the console. An evaluation license is created with your dock workspace; subscriptions are issued when an offer is accepted. See How licensing works.

What happens when the daily volume is exceeded? System Health alerts ("Allowed data volume exceeded"); dock shows plan versus actual. Reduce or route data with PortX, or move to a higher tier. See License and updates.

Are updates included? Yes, in every subscription and evaluation. See Release notes.

Security

Who can see my data? Only you: the customer is the sole data controller, XPLG has no access path by architecture, and support access, when you grant it, is VPN-only, MFA-enforced and logged. See Security posture.

Which sign-in methods? SAML 2.0 (Entra, Okta, ADFS), AD/LDAP with group mapping, Kerberos, OAuth/OpenID, header SSO, and an internal realm for air-gapped sites; MFA at the identity provider.

Can sensitive fields be masked? Yes, at ingestion with PortX Protect (mask, tokenize, encrypt by policy) and on the way out in forwarder flows. See Secure and Data handling.

Certifications? ISO/IEC 27001 certified ISMS; GDPR with a DPO; ISO 27017 and 27001 certificates on request through the Contact page of xplg.com.

Upgrades and support

How do I upgrade? V7: Publish Patch from System > About to every node; X8: change XPLG_IMAGE and up -d. Validate in five phases. See Upgrades.

Why does the patch refuse to deploy? The runtime is below Java 17 / Tomcat 10, the prerequisite build is missing, or the license is invalid. See License and updates.

Where do I get help? Email support@xplg.com first; the support portal, phone and online sessions follow from there. See Getting help. The product manual for V7-era detail remains on the XPLG wiki; this help center is the primary technical documentation.

Next: Getting help

Source: XPLG wiki, pages 3161980932, 3150774276, 1594132078, 1595637847, 1594132976, 1594133274, 3161489481, 3161718811, 3161489464, 1597964372, 1594131939 (https://xpolog.atlassian.net/wiki/spaces/XPOL/pages/1594131939).