QUESTION:
Does Enterprise Manager provide any tracking or statistics for Intelligence Server uptime in MicroStrategy 9.x?
ANSWER:
Enterprise Manager does not currently provide any tracking or statistics for Intelligence Server uptime, start time, stop time, etc. There is an existing Enhancement Request for this feature to be implemented in a future version of MicroStrategy.
Enterprise Manager does not currently provide any tracking or statistics for Intelligence Server uptime, start time, stop time, etc. There is an existing Enhancement Request for this feature to be implemented in a future version of MicroStrategy.
Contact MicroStrategy Technical Support for an update on the status of this Enhancement Request.
As a workaround, it should be possible for the system administrator to create a script or tool to parse the logging information recorded in the DSSErrors.log, and to subsequently determine when the Intelligence Server has started and stopped, calculating the uptime from this data.
Whenever the Intelligence Server starts, the first line that will be recorded in the DSSErrors.log is as follows:
<date> <time> [HOST:<hostname>][PID:<processid>][THR:<threadid>][Kernel][Info] SetEmergencyReserveSize(): New size = 8388608
Parsing the log output for this line should give a clear indication of each time the Intelligence Server starts.
Whenever the Intelligence Server stops normally, the last line that will be recorded in the DSSErrors.log is as follows:
<date> <time> [HOST:<hostname>][PID:<processid>][THR:<threadid>][Kernel][Info] MicroStrategy Intelligence Server shutdown normally
Parsing the log output for this line should give a clear indication of each time the Intelligence Server stops normally. It should be noted, though, is that this method will not account for any unexpected shutdowns of the Intelligence Server (due to crash, machine failure, power outage, etc), as the Intelligence Server would be unable to write to the log normally in such a situation.
The MicroStrategy Internal Reference Number for the Enhancement Request discussed in this technical note is 163972.