Attributes

Name Description
agentType [element Script] The agent type of which the script will run
agentType [type BaseMonitorType] The agent type
beginDate [element OneTimeMaintenanceWindow] The date and time when the one-time maintenance window starts (i.e., the moment in time when testing is suspended)
city [element MonitorSite] The city indicates where the Backbone node actually runs (e.g., New York, London, Beijing)
countryCode [element MonitorSite] The country code is a two letter abbreviation for the country where the Backbone node runs.
createDate [element MaintenanceWindowMonitor] The date on which the test was created
createDate [element MonitorSummary] The date on which a test was created
createDate [element ParameterizedMonitor] The date on which the test was created
createDate [element Script] The date when the script was created
createDate [type MonitorTypeForResponse] The date-time when the browser test was created
dateQueryType [type DateFilterType] The name of the operator used in a date filter
dateQueryType [type ExpDateFilterType] The name of the operator used in an expiration date filter
dayOfWeek [element RecurringMaintenanceWindow] The day of the week on which the maintenance window recurs
deletionFlag [element SubstitutionParameter] The deletionFlag is an attribute of the Substitution Parameter that is set only if the Substitution Parameter is to be deleted. Global substitution parameters cannot be deleted via the Test Management API because the Test Management API cannot manage references to Substitution Parameters within the script. However, site-level substitution parameters can be deleted. The effect of deleting a site-level substitution parameter is that the global substitution parameter value will be used.
description [element MonitorSummary] The description attribute contains the test name when it appears in a MonitorSummary.
endDate [element OneTimeMaintenanceWindow] The date and time when the one-time maintenance window stops (i.e., the moment in time when testing resumes)
endTime [element RecurringMaintenanceWindow] The time of day when testing resumes
expirationDate [type BaseMonitorType] This field contains the xsd:dateTime at which a test is expired. This field is optional, because not all tests expire.
folder [element MonitorOrderResponse] The name of the folder to which the browser test belongs This field maps to the description field of the monitor group.
folder [type BaseMonitorType] 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.
folderStatus [type MonitorTypeForProvisioning] 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.
folderStatus [type MonitorTypeForResponse] The status of the monitor group to which the browser test belongs Valid values are Active and Inactive.
frequencyInMins [element MonitorSummary] 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).
frequencyInMins [type BaseMonitorType] 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).
id [element SubstitutionParameter] An id (also called a ScriptSession_id) indicates the order in which the SubstitutionParameter was defined in the GSL script. If the GSL script contains three SubstitutionParameters, ids 0, 1, and 2 will be defined. If a site-level substitution parameter is subsequently created, it must have an id that matches one of the ids on the global substitution parameters. For example, if username is defined as the second substitution parameter in a script, its id will be set to 1 both in the global substitution parameter definition and in each site-level username definition.
includeRenderTimeFlag [type BaseMonitorType] This field is true if render time is to be captured in the test output and false if not. The default value is false.
ipV6Enabled [element MonitorSite] This field indicates whether the Backbone node supports IPv6. If true, the node supports IPv4 and IPv6. If false, the node only supports only IPv4.
ipVersion [element MonitorSummary] The version of the Internet protocol on which the test was configured to run This parameter limits the type of Backbone node on which the test may be deployed.
ipVersion [type BaseMonitorType] 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.
isPrivate [element MonitorSite] This indication is optionally provided by the system. It indicates whether the Backbone node is a private node (dedicated to a particular customer or test activity). If true, the node is private; if false, the node is not private.
modifyDate [element MaintenanceWindowMonitor] The date on which the test was last modified
modifyDate [element MonitorSummary] The date on which the test was last modified
modifyDate [element ParameterizedMonitor] The date on which the test was last modified
modifyDate [element Script] The date when the script was modified If the script was not modified, the modify date will be the same as the create date.
modifyDate [type MonitorTypeForResponse] The date-time when the browser test was last modified
monitorId [element MaintenanceWindowMonitor] A monitorId uniquely identifies a test within the Dynatrace Portal.
monitorId [element MonitorOrderResponse] The monitorId uniquely identifies the browser test in the system. This information must be sent whenever the browser test is updated or deleted.
monitorId [element MonitorSummary] The monitorId uniquely identifies the browser test in the system.
monitorId [element ParameterizedMonitor] A monitorId uniquely identifies a test within the Dynatrace Portal.
monitorId [element PartialUpdate] The monitorId uniquely identifies the browser test in the system.
monitorId [element TestStatusUpdateRequest/TestStatusUpdate] A monitorId uniquely identifies a test within the Dynatrace Portal.
monitorId [type MonitorTypeForResponse] The ID uniquely identifying the browser test
monitorStatus [element MaintenanceWindowMonitor] The current status of the test (Active or Inactive)
monitorStatus [element MonitorOrderResponse] The status of the test (Active, Inactive, or Deleted)
monitorStatus [element ParameterizedMonitor] The current status of the test (Active or Inactive)
monitorStatus [type MonitorTypeForProvisioning] The status of the browser test to be provisioned Valid values are Active and Inactive.
monitorStatus [type MonitorTypeForResponse] The status of the browser test Valid values are Active and Inactive.
name [element MonitorOrderResponse] The name of the browser test This field maps to the description column of a monitor defined in the monitor table of the database.
name [element MonitorProperty] The name of the test
name [element SubstitutionParameter] The name provides a human-readable reference to the substitution parameter.
name [type BaseMonitorType] The name of a browser test This field is mapped to the description column in the monitor table.
orderStatus [element MonitorOrderResponse] The status of the monitor order itself (SUCCESS if the test was successfully provisioned, FAILURE if the test could not be provisioned)
queryDate [type DateFilterType] The date in which a particular date in a test or script is compared when the filter is applied
scriptId [element Monitor] This field identifies the GSL script id used to create the test.
scriptId [element MonitorOrderResponse] This field identifies the GSL script id used to create the test.
scriptId [element MultiStepMonitor] This field identifies the GSL script id used to create the test.
scriptId [element Script] An identifier that uniquely identifies the Script in the system
siteId [element MonitorSite] The SiteId uniquely identifies the Backbone node within the Dynatrace Synthetic Monitoring Network.
siteId [type ProvisionTestsMonitorSitesType/MonitorSite] Since the ProvisionTestsMonitorSitesType is no longer used, neither is its siteId attribute.
siteName [element MonitorSite] The SiteName is a human-readable description of the site.
startTime [element RecurringMaintenanceWindow] The time of day when testing is suspended
state [element MonitorSite] The State indicates a larger region within a country where the Backbone node runs (e.g., New Jersey, New York, New Brunswick, Ile de France).
status [element MonitorSite] Backbone nodes may have one of three statuses: ACTIVE, INACTIVE, or DELETED. The GetSites query only returns ACTIVE sites.
status [element MonitorSummary] The Status of the test (Active or Inactive in this context)
status [element Script] The status of the Script: ACTIVE or INACTIVE
status [element TestStatusUpdateRequest/TestStatusUpdate] A test status may be Active, Inactive, or Deleted.
stepSeqNum [element Step] The ordinal number of the step within the sequence (starting with 0)
summaryFlag [element MonitorSummary] Indicates whether summary-level data was requested (to be accumulated in the data warehouse.
summaryFlag [type BaseMonitorType] This field is false if test data is captured at the component level and true if it is captured at the summary level.
value [element MonitorProperty] The value of a monitor property The value is a string but will be parsed to whatever type is required by the associated property name. For example, if the MonitorProperty's name is SummaryFlag, the value can be only On or Off. If the MonitorProperty's name is ExpirationDate, the value must be parsed to a DateTime object at least one day later than the current date.
value [element SubstitutionParameter] The value of the substitution parameter is the text that actually appears in a Script step in place of the Substitution Parameter reference. For example, if a GSL script step references the username substitution parameter, the value of the user name (e.g., "jsmith") is what will be used when the script is executed. In general Substitution Parameter values can be modified. The other data on the Substitution Parameter cannot be updated.