Background
While XpoLog is fully functional as an agentless application, i.e.. you can install it anywhere in the environment and import logs into its platform, it is also possible to install XpoLog as an agent or structure the deployment to several instances for several reasons which are specified below. If you choose to run multiple instances of XpoLog in the environment, it is possible to connect the different instances over HTTP/S (XpoLog to XpoLog).
When should XpoLog to XpoLog usage be considered?
There are several key reasons to consider installing multiple instances of XpoLog to manage an environment:
- 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?
Remote XpoLog installation is a regular installation, only with selected features activated. For example, if the remote XpoLog is used only to collect data to a centralized XpoLog then 'agent mode' is activated and no operations will be performed by the agent besides access to the data. In case a Map Reduce / multiple data centers deployment is required, then the remote XpoLog may be fully functional and all its log processing can be done independently. If the remote XpoLog is only used for Log Synchronization then 'agent mode' should be activated.
When deploying multiple remote XpoLog instances, it is possible to use a silent installation in order to distributed multiple setups and then remotely configure them by using the SDK commands.
How to connect between XpoLog instances?
In order to connect XpoLog instances and add the remote XpoLog's log to the centralized XpoLog instance, first ensure that there is communication over HTTP/S on the port which is used to run XpoLog between the instances:
- Go to XpoLog>Tools>Address Book, and 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).
- To add logs which are configured on the remote XpoLog follow information here: Adding Data to the XpoLog Platform / Adding Data to XpoLog
- To use the agent for a LogSync task, see Log Synchronization