MultiStepMonitor

Appears in a ProvisionTestsRequest. A MultiStepMonitor is the form of monitor order to be submitted when the test is being created based on an existing GSL script created in the Recorder and uploaded to the Dynatrace Portal (the opposite of a SingleStepMonitor, where the GSL is created on the fly based on a URL passed in the monitor order).

Derived by

Extending MonitorTypeForProvisioning

Attributes

Name Type Required? Default Description
scriptId string Yes This field identifies the GSL script id used to create the test.
monitorStatus MonitorStatusType Yes The status of the browser test to be provisioned. Valid values are Active and Inactive.
folderStatus MonitorStatusType No The status of the folder (monitor group) to be provisioned. May be set to Active or Inactive. If the folder already exists, its status will be updated and potentially trigger cascading changes for all the browser tests in the monitor group.
name string Yes The name of a browser test. This field is mapped to the description column in the monitor table.
folder string No The name of the folder containing the browser tests. This field is mapped to the description column of a monitor group in the monitor table.
agentType AgentType Yes The agent type.
summaryFlag FlagType No Off This field is false if test data is captured at the component level and true if it is captured at the summary level.
includeRenderTimeFlag FlagType No Off This field is true if render time is to be captured in the test output and false if not. The default value is false.
frequencyInMins int Yes This field captures the frequency in minutes with which a test is run on a Backbone node. The field is optional. The default frequency in minutes is 60 (one hour).
expirationDate dateTime No This field contains the xsd:dateTime at which a test is expired. This field is optional, because not all tests expire.
ipVersion IpVersionType No IPv6_preferred This field contains the ip mode of the test. The field is optional. The default value is IPv6_preferred. Valid values are IPv4_only, IPv6_only, and IPv6_preferred. Tests flagged as IPv6_only or IPv6_prefered may only be deployed to Backbone sites supporting IPv6.

Content model

Contains elements as defined in the following table.

Component Type Occurs Nillable? Description
SEQUENCE 1..1
MonitorSites anyType (restriction) 1..1 No The MonitorSites element is a container of MonitorSite elements. See MonitorSite for more information.

Referenced by

Example

<prov:ProvisionTestsRequest
   xmlns="http://www.gomeznetworks.com/schemas/provisioning">
   <prov:Credentials>
      <prov:UserName>erics</prov:UserName>
      <prov:Password>erics</prov:Password>
   </prov:Credentials>
   <prov:MultiStepMonitors>
     <prov:MultiStepMonitor name="EG 10-05-2012 001  Hotmail Auth with Params"
      folder="Hotmail Authentication" agentType="IE" frequencyInMins="60"
      monitorStatus="Inactive" scriptId="326334" ipVersion="IPv6_preferred">
        <prov:MonitorSites>
            <prov:MonitorSite siteId="880"/>
         </prov:MonitorSites>
      </prov:MultiStepMonitor>
   </prov:MultiStepMonitors>
</prov:ProvisionTestsRequest>