Logsign Health Check Notifications



Logsign health check service allows you to control important parameters and services from a single location for your system. If there will be a problem on any these services you will be notified through e-mail or SMS. It is possible to notify other users which is identified by system with SMS and e-mail except admin users.

Note : To configure e-mail and SMS settings you can read the "Mail Settings" and "SMS Settings" articles, also to identify users check "User Management" article. 


*Note : If Hotspot Module is not activated on Logsign platform (Hotspot Module is not included in your license) and if you do not have  "Radius Service Status" and cluster system, it is not necessary to activate "Namenode Service Status" health checks.



This feature is used to prevent breaking down the stability of system while the capacity of the disc is fulfilled that Logsign installed on this disk.

If you activate this feature;

When the fill rate of the disc is % 80, you will be notified with SMS or e-mail as written disc status : "Yellow" by Logsign. 

 When the fill rate is %90, it will inform you as written disc status : "Red"  and the collectors will not aggregate logs to the systems (poller-wmi, poller-wmi, syslog-collector, etc.) which is used to collect logs. The logs will not be written anymore on archive(.json), signed(.raw) and index. Thus, your disc will be prevented from filling until you interfere to the system.

** To allow the collecting logs again, the disc status must be "Green" and the fulfilled rate of the disc must be under %80.

When your system is installed on a virtual environment, you can increase the size of the disc and define a second disk. If your system is installed on a physical device, you can add a new disc and mount it to the system. (You can read this article about the disc expansion process on Linux.)

You can check the disc fulfilled rate from Disc Status chart under the Dashboard/ System section, as in the following screenshot admin panel:

If it is not convenient to add a new disc or the increase the size of the disc, you can back up the existing logs to a external environment and then you can increase the size of the disc through clearing logs on the Logsign platform. To see how to transfer the logs, check the Logsign Data Backup  article.

Moreover, you can plan the status of the disc through transferring the logs to the FTP Server which is defined under FTP Settings menu on Logsign platform. 


With this feature, you will be notified when the logs and signed logs settings   

 are changed. (You can check the signed logs settings under Settings/Data Management/Sign Settings on Logsign web interface.)

 In warning e-mail, it shows the problem with its date(yy/mm/dd) and file name. You can access the file which is under Settings/Data Management/Signed Logs from admin panel and verify the file according to the signature method via "Validate" button. As a result of that, it is possible to see the changed rows on log file.


 It must be activated to control change status of elastic search which is used as a database to observe instant results and contain the reports on Logsign.



It is the mechanism for controlling whether logs come to Logsign from integrated sources. While sources are integrated to Logsign, you can set the period of health check control as desired, as in the screen shot below:



If Hotspot module is active on the system:

This feature must be activated to establish controlling of FreeRadius service that provides AAA (authentication, authorization and accounting) audit, management of authentication and account data for users who can access to wireless network.  


When you activate this feature, it checks the status of web service that enables controlling of admin panel. 


Namenode works as a manager in Logsign cluster systems which is responsible for:

File access and distribution, creation, deletion and problem solution of processes overall servers. In brief, the information of all the files on HDFS (metadata) is stored and managed by Namenode.

It must be activated to check Namenode in cluster systems. 


Have more questions? Submit a request