Time to upgrade! You only have until October 31, 2019 to move to Dynatrace, our all-in-one software intelligence platform. For details, see the Synthetic Upgrade Center and Dynatrace Synthetic documentation.

GetLMAlertHistory (3.0)

This web method retrieves the alert history for all MBG monitors of a specific type within a specified time range.

Request parameters

To call this web service from your browser, submit the following HTTP Get Request:


In the URL above, specify the following parameters:

  • username – The Synthetic Classic account username
  • password – The Synthetic Classic account password
  • apitoken – The Synthetic Classic API token, used in lieu of username/password
  • monitorType – Specifies the class of MBG monitor data to retrieve. Specify one of the following values:
Value Description
ALL To return information for all monitor types ('PRIVATEPEER', 'MOBILE')
PRIVATEPEER To return information for PRIVATEPEER tests only
MOBILE To return information for MOBILE tests only
  • startTime — Start time for the request window in format* YYYY-MM-DD hh:mm:ss*
  • endTime — End time for the request window in format* YYYY-MM-DD hh:mm:ss*

If the request time frame (from startTime to endTime) is older than 45 days, data may not be returned, because data older than 45 days may not exist.

Validation criteria

This web service uses the following criteria to validate the incoming request:

  • username is valid for an active account.

  • password is valid for the specified username.

  • apitoken is the Synthetic Classic API token, used in lieu of username/password.

  • monitorType specifies a valid MBG monitor class.

  • startTime has a valid date/time format.

  • endTime has a valid date/time format.

  • The size of the request time frame (difference between startTime and endTime) must be less than or equal to 24 hours.

Response XML

This web service method returns information according to its operation status.

If the web service operation fails, the FAILED status and an error message are returned in the following XML format.

<?xml version="1.0" encoding="utf-8"?>
<lastmileAlertHistoryResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  <errorMessage>Invalid Account Specified</errorMessage>

If the web service operation succeeds, the information requested is returned in the following XML format.


The following table summarizes the main elements, attributes, and possible attribute values in the XML response returned by this web service. See the Alert Management WSDL for the complete definition of this XML response.

XML Elements & Attributes Description Parent Element Child Elements
<alertHistoryResponse> Top-level container of the XML response of this web service none <status> <errorMessage> <alertSummary>
<status> SUCCESS | FAILED <lastmileAlertHistoryResponse> none
<errorMessage> Detailed error message if status="FAILED" <lastmileAlertHistoryResponse> none
<alertSummary> Container for alert summary information and alert payload <lastmileAlertHistoryResponse> <messagePayload>
messageId Synthetic Classic message ID
monitorId MBG monitor ID
alertId The following integral values are possible for the different alert types:
  • 101 — Transaction Failure
  • 102 — Response Time Failure
alertType The following values correspond to alertId values:
  • Transaction Failure (alertId=101)
  • Response Time Failure (alertId=102)
alertState The following values for the current state of the alert are possible:
  • Good — No user-specified criteria has been violated.
  • Bad — Indicates a violation of user-specified non-response-time criteria.
  • Warning — Indicates a violation of user-specified response time criteria.
  • Severe — Indicates a violation of user-specified response time criteria.
progression The following values for progression are possible:
  • Initial — First alert sent in alertState.
  • Reminder — Alert sent repeatedly.
  • Condition Improved — alertState has changed from an alertable to a non-alertable state.
<messagePayload> Container for actual alert payload <alertSummary>