Page Comparison

...

• Inaccessible network segments – Sometimes, when logs are collected from multiple network segments, there is no direct access between the location of the centralized XpoLog to other network segments (for instance, different domains in Windows). 
• Data load balancing (Map Reduce) – In cases where a regular cluster is insufficient, it is possible to manage several XpoLog instances of several separate machines, and each will be managing a selected group of logs, and on top of all instances, there will be an instance which users can access to view all logs from all instances.
• Keeping main console on Linux in a mixed Linux/Windows environment – In case the main XpoLog instance runs on Linux/Solaris, but there is a need to add logs from Windows machines (Windows event logs, logs on shared locations, Windows machines), it is mandatory to deploy a Windows instance of XpoLog which will be able to manage all logs from Windows machines and connect it to the centralized XpoLog instances.
• Different data centers – Organizations which manage multiple data centers may consider an XpoLog cluster/instance per data center to get optimized connectivity and performance within each data center and then connect all data centers instances to a centralized XpoLog instance for the users.
• Need of an agent to collect data – While XpoLog is completely agentless, in cases where there is no available connectivity to the sources with the standard protocols, it is recommended to install XpoLog as an agent on the remote sources and collect the data from using XpoLog to XpoLog communication over HTTP/S protocol. The agent is also required for Log Synchronization to collect data as is from multiple sources into a central repository.
• Need of a Forwarder - XpoLog forwarder/SysLog TCP/UDP forwarder/ HTTP/HTTPS Forwarder. This option can be used when a specific environment is set to use XPLG to normalize & push data to a central XpoLog.

How to install a remote XpoLog?

...