XPLG deployment planning
Use this topic as a pre-deployment checklist. Complete the steps below-especially sizing, topology, and connectivity-before you install or expand XPLG in production. Read the referenced documentation in full; if anything is unclear, contact XPLG Support before go-live. Validate all changes in a staging environment before deploying or upgrading production.
1. Platform, sizing, and topology
1.1 System requirements
Review the official system requirements for your target environment to determine:
Supported operating system (e.g. Windows, Linux).
Whether a cluster is required for your availability, scale, or operational model.
Network requirements, including firewall rules and open ports between components, clients, and data sources.
1.2 Capacity planning
Before installation, capture at least:
Estimated daily log volume (ingest rate and retention expectations).
Expected number of concurrent users (interactive search and UI load).
1.3 Deployment architecture
For small environments (approximately under 10 GB per day), a single XPLG process handling both processing and search may be acceptable. For higher volumes, strongly recommended practice is to run the processor on a dedicated instance and the UI on a dedicated instance. For detailed sizing and hardware guidance, see system requirements and deployment sizing documentation.
2. Installation
Install the XPLG server or cluster according to the installation guide for your platform. Use the capacity figures from system requirements to confirm node roles and counts.
3. Post-installation hardening and baseline configuration
After installation, apply post installation recommendations from the product documentation. Typical areas include (where applicable to your edition and deployment):
Security (access control, TLS, integration with corporate identity).
Time synchronization, logging, and monitoring of the XPLG hosts themselves.
Storage paths, retention, and backup or disaster-recovery alignment with IT standards.
JVM or service tuning per official guidance for your workload.
Adjust this list to match your organization’s policies and the current Administrator Guide.
4. Log sources: planning and grouping
Configure log sources as described in the Administrator Guide. Use the following planning sequence before bulk configuration.
4.1 Remote access and connectivity
For each source or source class, determine:
How data will be collected (e.g. direct file access, database, SSH, API, agent, syslog-per your environment).
What network paths, credentials, and protocols are required so connectivity can be provisioned and tested early.
4.2 Source characteristics
Within each source type, document attributes that affect configuration-for example host role, application ownership, region, or compliance zone-so policies and templates stay consistent.
4.3 Organization: applications and folders
Define how sources will be grouped (e.g. by application, system, team, or geography). In XpoLog, Applications and Folders provide the hierarchy for navigation and administration. A source may belong to multiple groups when that reflects your topology (e.g. one source under an application and under a regional folder).
These structures also drive tag-oriented dashboards, saved searches, and monitors scoped to folder, log, server, or application—plan groups so those artifacts remain maintainable as you scale.
5. Log templates
Create detailed log templates for your primary log types before large-scale ingestion. Templates can be refined later; early definition reduces misclassification and rework when volume grows.
6. Begin ingestion
When planning, installation, post-install steps, and source/template design are complete, onboard data from your sources per the Administrator Guide, validating parsing, retention, and access in staging first.
Support and production cutover
For questions or concerns at any stage, contact XPLG Support. Perform full testing in staging before production deployment or upgrade.