Enable sending Sisense monitoring logs [Windows]
This article explains how to troubleshoot the connection to the Sisense Monitoring Module in Sisense Windows installations.
Sisense Windows collects data when you or your users install or use Sisense products or services. Sisense uses the data collected for internal and support-related purposes such as improving our products and services, improving customer engagement, conducting research, and resolving technical issues.
This article outlines how to resolve issues with logs not reaching the monitoring service.
This article is only applicable to external Sisense monitoring. In-application tracking is available via the Usage Analytics feature.
If necessary, to disable monitoring, please reference this article: Disable Monitoring Logs From Being Sent To Monitoring Service
What to Check:
The external monitoring is only available for Sisense Windows versions W2023.9 and above. In case of earlier Sisense versions, you need to upgrade your installation.
Services: Make sure that the appropriate services are running:
- Sisense.Collector,
- Sisense.Shipper
and
- Sisense.Housekeeper.
If one or both are not running, be sure to start these services.
Shipper Config:
C:\ProgramData\Sisense\Infra\Data\Shipper\Config\shipper.conf
​Port: Our monitor agent is streaming data on HTTPS (port 443). If, for some unlikely reason, your network security settings block such traffic by default, please make sure you create an outbound rule for TCP port 443.
You can verify the connection by initiating a Telnet session to our server:
telnet ingress.eu2.coralogix.com 443
It will take 15- 30 minutes for these changes to impact whether logs are sent. If these steps have not helped with allowing logs to be sent, please create a ticket with our Support team.
References/Related Content
Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.
