App_Features_Service

<back to all web services

HealthCheckRequest

The following routes are available for this service:
GET/healthcheckThe request for getting health check information.Depending on the execution mode, you can determine different states of the server.
HealthCheckRequest Parameters:
NameParameterData TypeRequiredDescription
ExecutionModequeryExecutionModeYesThe mode used to determine what level of health check to perform.

Allowable Values

  • Basic
  • Standard
  • Advanced
ServerTypequeryServerTypeYesThe type of server that will be used to determine which monitors will be run.

Allowable Values

  • App
  • Sql
  • FtpApi
  • Ftp
  • Batch
  • Identity
  • Qc
  • XcodeV
  • XcodeC
  • MsgVast
  • AsgVast
  • Mongo
  • Agents
IncludeServerStateInformationquerybooleanNoIndicates whether or not to include server state information in the response.
SuppressErrorCodesquerybooleanNoIndicates whether or not to suppress returning error codes. This will always return a 200 code to the caller, which is required for PRTG to process the JSON response properly.
SuppressDeploymentErrorsquerybooleanNoIndicates whether or not to suppress deployment-related errors.
ExecutionMode Enum:
NameValue
Basic1
Standard2
Advanced3
ServerType Enum:
NameValue
App1
Sql2
FtpApi3
Ftp4
Batch5
Identity6
Qc7
XcodeV8
XcodeC9
MsgVast10
AsgVast11
Mongo12
Agents13
HealthCheckResponse Parameters:
NameParameterData TypeRequiredDescription
ServerStateformServerStateNo
StatusformMonitoringStatusNo
StatusMessageformstringNo
CorrelationIdformstringNo
FailedMonitorCountformintNo
MonitorSummariesformList<MonitorSummary>No
ExecutionMetricsformMonitorExecutionMetricsNo
ServerState Parameters:
NameParameterData TypeRequiredDescription
ServerNameformstringNo
TotalRamInMbformdecimal?No
AvailableRamInMbformdecimal?No
UsedCpuPercentformdecimal?No
MonitoringStatus Enum:
NameValue
Success1
Failure2
MonitorSummary Parameters:
NameParameterData TypeRequiredDescription
MonitorNameformstringNo
StatusformMonitoringStatusNo
ResultsformList<MonitoringResult>No
ErrorMessagesformList<string>No
MonitoringResult Parameters:
NameParameterData TypeRequiredDescription
MonitoringNameformstringNo
StatusformMonitoringStatusNo
StatusMessageformstringNo
ErrorMessagesformList<string>No
MonitorExecutionMetrics Parameters:
NameParameterData TypeRequiredDescription
StartDateTimeformDateTimeNo
EndDateTimeformDateTimeNo
DurationformTimeSpanNo

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

GET /healthcheck HTTP/1.1 
Host: 54.235.149.200 
Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"ServerState":{"ServerName":"String","TotalRamInMb":0,"AvailableRamInMb":0,"UsedCpuPercent":0},"Status":"Success","StatusMessage":"String","CorrelationId":"String","FailedMonitorCount":0,"MonitorSummaries":[{"MonitorName":"String","Status":"Success","Results":[{"MonitoringName":"String","Status":"Success","StatusMessage":"String","ErrorMessages":["String"]}],"ErrorMessages":["String"]}],"ExecutionMetrics":{"StartDateTime":"\/Date(-62135596800000-0000)\/","EndDateTime":"\/Date(-62135596800000-0000)\/","Duration":"PT0S"}}