...
While XpoLog is fully functional as an agent-less application, Ii.e.E. you can install it anywhere in the environment and import the logs into platform, it is also possible to install XpoLog as an agent or to structure the deployment to several instances from for several reason reasons which are specified below. If you choose to do run multiple instances of XpoLog in the environment, it is then possible to connect the different instances over HTTP/S (XpoLog to XpoLog).
...
- 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 in 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 instances of 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 agent-less, 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 source and collect the data from this source using XpoLog to XpoLog HTTP/S protocol.
...
Remote XpoLog installation is a regular installation only with select features activated. For example, if the remote XpoLog is used only to collect data then indexing and , Analytics should be disabled on it. In case a Map Reduce / Different data centers deployment is required then , the remote XpoLog is fully functional and all its log processing will be done independently.
...
In order to connect XpoLog instances and add the remote XpoLog's log to the centralized XpoLog instance first ensure there is communication over HTTP/S on the port which is used to run XpoLog between the instances. Then follow these steps (more details are available at add data to XpoLog):
- Go to XpoLog>Tools>Address Book, add a remote XpoLog account with all the required details (a user name and password are also required if security is activate on the remote XpoLog).
- Go to XpoLog>Administration>Add Log, select log type - Remote XpoLog, and select all or part of the logs from the remote instance.
- Save it and all the remote logs will be available under the Folders and Logs tree.