OVERVIEW
Consider a scenario where Strategy Intelligence Server is installed on Windows and users wish to enable logging through Telemetry Server (Messaging Services.) In certain cases, it may be desired to install Telemetry Server on a remote computer and configure logging through the remote Telemetry Server instead of the local Telemetry Server that is bundled with the installation of the Intelligence Server. For example, a user may have an existing installation of Intelligence Server on Windows but wants to use Telemetry Server installed on a Linux box in order to avoid the issue from KB441447.
The following steps describe how to direct Intelligence Server to send data to the remote Telemetry Server. The following steps will assume that Telemetry Server has already been installed remotely and the underlying services, Kafka and Zookeeper are running.
CONFIGURATION STEPS
1. Once Telemetry Server has been installed remotely run the following Command Manager outlines against the Intelligence Server on Windows to enable Messaging Services and logging through Telemetry Server. In the first outline <Telemetry Server IP> and <Telemetry Server port> should be updated with the correct values respectively.
ALTER SERVER CONFIGURATION ENABLEMESSAGINGSERVICES TRUE CONFIGUREMESSAGINGSERVICES "bootstrap.servers:<Telemetry Server IP>:<Telemetry Server port>/batch.num.messages:5000/queue.buffering.max.ms:2000";
ALTER FEATURE FLAG "SENDING LOG TO MESSAGING SERVICES" ON;