Monitoring

Owned by Bernhard Wolkerstorfer (Unlicensed)
Last updated: Apr 11, 2016

The eRecruiter should be monitored using monitoring tools (i.e. nagios). It may also be monitored using a specialized performance monitoring solution to get deep insight (i.e. NewRelic, ruxit).

Server

The following metrics are the minimal recommended monitoring metrics:

  • CPU usage (alarm if > 95% for 10 minutes)
  • RAM usage (alarm if > 90% for 10 minutes)
  • HDD usage (alarm if > 90% for 10 minutes)
  • HDD and network I/O (alarms a required)

Microsoft SQL Server

The following metrics are the minimal recommended monitoring metrics:

  • Database HDD usage (alarm at 90%)
  • Transaction logs HDD usage (alarm at 90%)
  • Transaction log usage (alarm at 80%)
  • Number of database locks, queue wait time and MSSQL performance metrics

IIS Applications

The eRecruiter IIS applications should be monitored for abnormal usage and reachability.

  • Check for reachability of the application (TCP port, HTTP response status)
  • IIS application pool memory usage 

eRecruiter Cron Worker

The eRecruiter Cron Worker can be monitored using a simple SQL script that will calculate the latest execution and can be monitored using standard monitoring tools.

SELECT TOP 1     
  [Date] AS 'LastRun', 
  CAST(CASE WHEN DATEDIFF(hour, [Date], SYSDATETIME()) > 1 THEN 'FAILURE' ELSE 'OK' END AS nvarchar) AS 'Status'
FROM 
  [ecBase].[CronWorkerLog]
ORDER BY
  [Date] DESC

It is recommended to execute the monitoring script every 15 minutes and set the alarm after 3 FAILURE responses. After alarm status is reached the check interval should be reduced to 5 minutes until the alarm has been cleared.

eRecruiter Media Service

It is recommended to monitor the eRecruiter Media Service as it is responsible to create documents and printouts.

  • Monitoring of the TCP port the eRecruiter Media Service is listening on.
  • Monitoring of the eRecruiter Media Service process.

Â