When using DirSearch responses for monitoring what is a reasonable response time before triggering an alert? - c06330101
Some customers use DirSearch as a measure of the health of the service. When doing this, below are some expectations when using the API for monitoring
When using DirSearch for health monitoring, use SearchByPrinterNum to perform the health check.
- This check uses a constant printer to ensure consistent and regular results that are not impacted by the configuration.
- Expected Response times should be less than 1 second.
- See example link below:
http://server.com/cps/DirSearch?ponAPIfunc=DirSearch&clientSWKey=clientKey&clientSWName=MyPairApp&clientSWVer=3.2.2&searchType=searchByPrinterNum&searchPrinterNum=900784151735
NOTE:
Applies to PrinterOn Enterprise 3.x and later.