LastMileMonitorOrderResponse elements appear in both ProvisionLastMileTestsResponse elements. They contain information about a monitor-level transaction that either completed successfully or failed to complete successfully.

Derived by

Restricting anyType


Name Type Required? Default Description
name string Yes The name of the browser test. This field maps to the description column of a monitor defined in the monitor table of the database.
folder string No The name of the folder to which the browser test belongs. This field maps to the description field of the monitor group.
monitorId string Yes The monitorId uniquely identifies the browser test in the Dynatrace Portal for the account. This information must be sent whenever the browser test is updated or deleted.
mbgmonitorId string Yes The mbgmonitorId uniquely identifies the MBG monitor that was tested.
mbgId string Yes The mbgId uniquely identifies the MBG that was tested.
monitorStatus MonitorStatusType Yes The status of the test (Active, Inactive, or Deleted).
orderStatus ResponseStatusType Yes The status of the monitor order itself (SUCCESS if the test was successfully provisioned, FAILURE if the test could not be provisioned.

Content model

Contains elements as defined in the following table.

Component Type Occurs Nillable? Description
Message [element MonitorOrderResponse] string 0..1 No This is an error message at the level of a specific monitor order response. However, even if there is no error, message is populated with a description of the outcome of the monitor order. Use the orderStatus field to determine the outcome of the provisioning attempt and the message as a container of supporting data.

Referenced by


The following example shows the role that LastMileMonitorOrderResponse elements play in a ProvisionLastMileTests operation invocation:

      <LastMileMonitorOrderResponse name="Test" folder="TestFolder" monitorId="542453"
            mbgmonitorId="16755" mbgId="15088" monitorStatus="Active"
      <LastMileMonitorOrderResponse name="Test2" folder="TestFolder2" monitorId="542787"
            mbgmonitorId="14525" mbgId="16258" monitorStatus="Active"

In the previous example, the ProvisionLastMileTests request caused two transactions to be initiated. The first completed successfully, resulting in the creation of a test with monitorId 542453. The second transaction failed. The ResponseStatus for the entire request is listed as a failure because of the failure encountered in the second transaction.