This monitoring endpoint serves the purpose of enabling MG+ to detect any network issues between MG+ and the operators' application.
By implementing this method, MG+ will be able to provide better support for ongoing operations through regular network monitoring. This will enable MG+ to proactively address any latency issues by pinpointing the underlying cause: whether it is a network problem between MG+ and the operator, or an internal processing bottleneck on the operator's side.
While MG+ typically calls this method every minute as part of its routine monitoring, during problem debugging, it may need to make manual calls to gain additional information. The overall number of calls made would not exceed the limit of 1500 calls per day.
GET {base_url}/monitor
Request Data
|
Name |
Required |
Data Type |
Description |
|---|---|---|---|
|
ping |
Yes |
String (255) |
Value provided by the caller, which could be any URL encoded string. |
Example Request
/monitor?ping=Test%20Monitor
Response Data
|
Name |
Required |
Data Type |
Description |
|---|---|---|---|
|
pong |
Yes |
String (255) |
Response value must be equal to the URL decoded value provided in the ping parameter. |
Example Response
{
"pong": "Test Monitor"
}
HTTP Response Codes
|
Status Code |
Description |
Example |
|---|---|---|
|
200 |
OK |
|