Try it free

Synthetic events

  • Latest Dynatrace
  • Reference

Definition of Synthetic events.

Synthetic HTTP step execution details

Synthetic HTTP step execution details event

Synthetic base event fields

The following base fields are used for synthetic events.

AttributeTypeDescriptionExamples

timestamp

timestamp

stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created.

1649822520123123123

event.id

string

stableUnique identifier string of an event; is stable across multiple refreshes and updates.

5547782627070661074_1647601320000

event.version

string

stableDescribes the version of the event.

1.0.0

event.type

string

stableThe unique type identifier of a given event.Tags: permission

ESXI_HOST_MEMORY_SATURATION; PROCESS_RESTART; CPU_SATURATION; MEMORY_SATURATION; Automation Workflow; AppEngine Functions - Small

event.kind

string

stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event. 1Tags: permission

SYNTHETIC_EVENT

1

Fixed value SYNTHETIC_EVENT.

Synthetic primary tags fields

The following fields are common for all synthetic events.

AttributeTypeDescriptionExamples

dt.synthetic.monitor.id

string

experimentalThe identifier of the monitor.

HTTP_CHECK-6349B98E1CD87352

dt.entity.synthetic_test

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST.Tags: entity-id

SYNTHETIC_TEST-A140F3B85BCCBD1A

dt.entity.http_check

string

resource stableAn entity ID of an entity of type HTTP_CHECK.Tags: entity-id

HTTP_CHECK-A140F3B85BCCBD1A

dt.entity.multiprotocol_monitor

string

resource stableAn entity ID of an entity of type MULTIPROTOCOL_MONITOR.Tags: entity-id

MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A

dt.entity.external_synthetic_test

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A

monitor.name

string

experimentalThe name of the monitor.

Monitor name

dt.synthetic.step.id

string

experimentalThe identifier of the monitor step.

HTTP_CHECK_STEP-5349B98E1CD87352

dt.entity.synthetic_test_step

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST_STEP.Tags: entity-id

SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

dt.entity.http_check_step

string

resource stableAn entity ID of an entity of type HTTP_CHECK_STEP.Tags: entity-id

HTTP_CHECK_STEP-A140F3B85BCCBD1A

dt.entity.external_synthetic_test_step

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

step.name

string

experimentalThe name of the step.

Step name

step.sequence_number

long

experimentalThe sequence number of the step (numbered from 0).

0

dt.synthetic.monitored_entity_ids

array

experimentalIDs of monitored entities.

APPLICATION-EA7C4B59F27D43EB

primary_tags.__key__

string

experimentalUser-defined primary grail tags, __key__ prefixed with primary_tags.. The value is a string.

tag-value; value

dt.security_context

string

resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: permission

Synthetic step result fields

The following result fields are used for synthetic monitor step execution events.

AttributeTypeDescriptionExamples

result.state

string

experimentalResult state of monitor execution.

FAIL

result.state MUST be one of the following:

ValueDescription

FAIL

Fail

SUCCESS

Success

Synthetic HTTP step execution details fields

AttributeTypeDescriptionExamples

custom_logs

record[]

experimentalA collection of custom log lines

Synthetic HTTP step execution details result statistics fields

AttributeTypeDescriptionExamples

result.statistics.method

string

experimentalHTTP request method.

GET; POST; HEAD

result.statistics.peer_certificate_details

string

experimentalThe peer certificate details.

Signature Algorithm: SHA256withRSA

result.statistics.request.header.__key__

string

experimentalHTTP request headers, __key__ being the lowercase HTTP header name, e.g. "http.request.header.accept-encoding". The value is a string.

https://www.foo.bar/; gzip, deflate, br; 1.2.3.4, 1.2.3.5

result.statistics.request_body

string

experimentalThe request body.

request body

result.statistics.resolved_ips

record[]

experimentalA collection of resolved ips.

result.statistics.response.header.__key__

string

experimentalHTTP response headers, __key__ being the lowercase HTTP header name, e.g. "http.response.header.content-type". The value is a string.

909; text/html; charset=utf-8; abc, def

result.statistics.response_body

string

experimentalThe response body.

response body

result.statistics.response_message

string

experimentalThe response message.

OK

result.statistics.url

string

experimentalThe HTTP request url.

www.dynatrace.com

Synthetic batch status

Synthetic batch status event

Synthetic base event fields

The following base fields are used for synthetic events.

AttributeTypeDescriptionExamples

timestamp

timestamp

stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created.

1649822520123123123

event.id

string

stableUnique identifier string of an event; is stable across multiple refreshes and updates.

5547782627070661074_1647601320000

event.version

string

stableDescribes the version of the event.

1.0.0

event.type

string

stableThe unique type identifier of a given event.Tags: permission

ESXI_HOST_MEMORY_SATURATION; PROCESS_RESTART; CPU_SATURATION; MEMORY_SATURATION; Automation Workflow; AppEngine Functions - Small

event.kind

string

stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event. 1Tags: permission

SYNTHETIC_EVENT

1

Fixed value SYNTHETIC_EVENT.

Synthetic primary tags fields

The following fields are common for all synthetic events.

AttributeTypeDescriptionExamples

dt.synthetic.monitor.id

string

experimentalThe identifier of the monitor.

HTTP_CHECK-6349B98E1CD87352

dt.entity.synthetic_test

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST.Tags: entity-id

SYNTHETIC_TEST-A140F3B85BCCBD1A

dt.entity.http_check

string

resource stableAn entity ID of an entity of type HTTP_CHECK.Tags: entity-id

HTTP_CHECK-A140F3B85BCCBD1A

dt.entity.multiprotocol_monitor

string

resource stableAn entity ID of an entity of type MULTIPROTOCOL_MONITOR.Tags: entity-id

MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A

dt.entity.external_synthetic_test

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A

monitor.name

string

experimentalThe name of the monitor.

Monitor name

dt.synthetic.step.id

string

experimentalThe identifier of the monitor step.

HTTP_CHECK_STEP-5349B98E1CD87352

dt.entity.synthetic_test_step

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST_STEP.Tags: entity-id

SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

dt.entity.http_check_step

string

resource stableAn entity ID of an entity of type HTTP_CHECK_STEP.Tags: entity-id

HTTP_CHECK_STEP-A140F3B85BCCBD1A

dt.entity.external_synthetic_test_step

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

step.name

string

experimentalThe name of the step.

Step name

step.sequence_number

long

experimentalThe sequence number of the step (numbered from 0).

0

dt.synthetic.monitored_entity_ids

array

experimentalIDs of monitored entities.

APPLICATION-EA7C4B59F27D43EB

primary_tags.__key__

string

experimentalUser-defined primary grail tags, __key__ prefixed with primary_tags.. The value is a string.

tag-value; value

dt.security_context

string

resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: permission

Batch status fields

AttributeTypeDescriptionExamples

batch.status

string

experimentalThe status of the batch.

Success; Failed

batch.source

string

experimentalThe source of the batch.

PUBLIC_API

configuration.fail_on_performance_issue

boolean

experimentalInformation whether performance issue validation was enabled.

true

configuration.fail_on_ssl_warning

boolean

experimentalInformation whether ssl certificate validation was enabled.

true

configuration.take_screenshot_on_success

boolean

experimentalInformation whether the execution should provide a screenshot in case of success.

true

configuration.processing_mode

string

experimentalThe execution's processing mode

DISABLE_PROBLEM_DETECTION

failed_executions

record[]

experimentalA collection of failed execution objects. Information about on-demand executions that failed.

failed_to_execute

record[]

experimentalA collection of failed execution objects. Information about on-demand executions that failed to be executed.

triggering_problems

record[]

experimentalA collection of triggering problem objects. The details of problems encountered while triggering on-demand executions.

metadata.__key__

string[]

experimentalThe metadata properties of the batch. 'key' being the metadata key. The value is a string defined by a user.

['"metadata.version": "1.255.20221022"']

triggered_executions

long[]

experimentalA collection of triggered executions ids.

[12345, 23456]

batch.status MUST be one of the following:

ValueDescription

Failed

Failed

Failed to execute

Failed to execute

Not triggered

Not triggered

Running

Running

Success

Success

batch.source MUST be one of the following:

ValueDescription

PUBLIC_API

API

UI

UI

configuration.processing_mode MUST be one of the following:

ValueDescription

DISABLE_PROBLEM_DETECTION

DISABLE_PROBLEM_DETECTION

EXECUTIONS_DETAILS_ONLY

EXECUTIONS_DETAILS_ONLY

STANDARD

STANDARD

Batch result fields

Batch result

AttributeTypeDescriptionExamples

batch_result.triggered_count

long

experimentalThe number of triggered executions within the batch.

6

batch_result.executed_count

long

experimentalThe number of triggered executions with the result SUCCESS or FAILED.

5

batch_result.failed_count

long

experimentalThe number of triggered executions with the result FAILED.

4

batch_result.failed_to_execute_count

long

experimentalThe number of executions that were triggered and not executed because of a problem with the Synthetic engine.

3

batch_result.triggering_problems_count

long

experimentalThe number of executions that were not triggered due to some problems.

2

batch_result.duration

duration

experimentalThe duration of the batch execution.

456

batch_result.total_duration

duration

experimentalThe sum of duration of the sum of all executions in batch.

1567

Synthetic batch status fields

AttributeTypeDescriptionExamples

user.id

string

stableUnique UUID of a human user. If the system itself has to be represented, the constant 'system' is used.

35ba9499-f87c-4047-962c-14dc32e255e5; system

Synthetic browser monitor execution

Synthetic browser monitor execution event

Synthetic base event fields

The following base fields are used for synthetic events.

AttributeTypeDescriptionExamples

timestamp

timestamp

stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created.

1649822520123123123

event.id

string

stableUnique identifier string of an event; is stable across multiple refreshes and updates.

5547782627070661074_1647601320000

event.version

string

stableDescribes the version of the event.

1.0.0

event.type

string

stableThe unique type identifier of a given event.Tags: permission

ESXI_HOST_MEMORY_SATURATION; PROCESS_RESTART; CPU_SATURATION; MEMORY_SATURATION; Automation Workflow; AppEngine Functions - Small

event.kind

string

stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event. 1Tags: permission

SYNTHETIC_EVENT

1

Fixed value SYNTHETIC_EVENT.

Synthetic primary tags fields

The following fields are common for all synthetic events.

AttributeTypeDescriptionExamples

dt.synthetic.monitor.id

string

experimentalThe identifier of the monitor.

HTTP_CHECK-6349B98E1CD87352

dt.entity.synthetic_test

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST.Tags: entity-id

SYNTHETIC_TEST-A140F3B85BCCBD1A

dt.entity.http_check

string

resource stableAn entity ID of an entity of type HTTP_CHECK.Tags: entity-id

HTTP_CHECK-A140F3B85BCCBD1A

dt.entity.multiprotocol_monitor

string

resource stableAn entity ID of an entity of type MULTIPROTOCOL_MONITOR.Tags: entity-id

MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A

dt.entity.external_synthetic_test

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A

monitor.name

string

experimentalThe name of the monitor.

Monitor name

dt.synthetic.step.id

string

experimentalThe identifier of the monitor step.

HTTP_CHECK_STEP-5349B98E1CD87352

dt.entity.synthetic_test_step

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST_STEP.Tags: entity-id

SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

dt.entity.http_check_step

string

resource stableAn entity ID of an entity of type HTTP_CHECK_STEP.Tags: entity-id

HTTP_CHECK_STEP-A140F3B85BCCBD1A

dt.entity.external_synthetic_test_step

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

step.name

string

experimentalThe name of the step.

Step name

step.sequence_number

long

experimentalThe sequence number of the step (numbered from 0).

0

dt.synthetic.monitored_entity_ids

array

experimentalIDs of monitored entities.

APPLICATION-EA7C4B59F27D43EB

primary_tags.__key__

string

experimentalUser-defined primary grail tags, __key__ prefixed with primary_tags.. The value is a string.

tag-value; value

dt.security_context

string

resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: permission

Synthetic execution event fields

The following base fields are used for synthetic execution events.

AttributeTypeDescriptionExamples

execution.type

string

experimentalThe type of the execution.

on-demand

execution.end_timestamp

timestamp

experimentalThe timestamp when execution was finished, in UTC milliseconds.

1629891695487

dt.synthetic.batch.id

long

experimentalThe identifier of the batch (defined for on-demand executions only).

dt.entity.synthetic_location

string

resource stableAn entity ID of an entity of type SYNTHETIC_LOCATION.Tags: entity-id

SYNTHETIC_LOCATION-D140F3B85BCCBD1A

execution.type MUST be one of the following:

ValueDescription

on-creation

on-creation

on-demand

on-demand

on-demand with customized script

on-demand with customized script

on-update

on-update

re-run

re-run

standard

standard

Synthetic result status fields

The following status fields are used for synthetic execution events.

AttributeTypeDescriptionExamples

result.status.details

string

experimentalStatus details.

connection timed out after 5000 ms: google.com

result.status.on_demand.message

string

experimentalThe on-demand status message.

Success

result.status.on_demand.details

string

experimentalThe details of the status.

PERFORMANCE_THRESHOLD_VIOLATION

result.status.category

string

experimentalThe category of the status.

FAIL

result.status.code

long

experimentalNumeric representation of the status.

599

result.status.message

string

experimentalThe message returned by an execution or a status message.

TIMEOUT

result.status.category MUST be one of the following:

ValueDescription

FAIL

Execution fail

NOT_EXECUTED

Not executed

SUCCESS

Success

UNEXPECTED_ERROR

Unexpected error

Monitor result fields

The following result fields are used for synthetic monitor execution events.

AttributeTypeDescriptionExamples

result.failed_step.name

string

experimentalThe name of the failed step

Second step

result.failed_step.sequence_id

long

deprecatedThe sequence ID of the step. Replaced by result.failed_step.sequence_number

2

result.failed_step.sequence_number

long

experimentalThe sequence id of the step.

2

result.executed_steps_count

long

experimentalThe number of executed steps.

2

result.engine.id

long

experimentalThe id of the engine which has executed the monitor.

123

result.location.type

string

experimentalThe type of synthetic location.

private

result.state

string

experimentalResult state of monitor execution.

FAIL

dt.active_gate.id

string

resource experimentalHexadecimal identifier of the ActiveGate prefixed with 0x

0xef3d21c3

result.location.type MUST be one of the following:

ValueDescription

private

Private

public

Public

result.state MUST be one of the following:

ValueDescription

FAIL

Fail

SUCCESS

Success

Synthetic browser monitor execution fields

AttributeTypeDescriptionExamples

dt.entity.synthetic_test

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST.Tags: entity-id

SYNTHETIC_TEST-A140F3B85BCCBD1A

execution.retry_on_error

boolean

experimentalShould we ignore this execution attempt (which was a failure) - will there be retry.

true

execution.screen_capture

string

experimentalScreen capture mode

capture_on_error

next_execution.id

long

experimentalNext execution id for sequential mode.

100681465183

reference_execution.id

long

experimentalRetried execution's id.

100681465183

result.failed_step.id

string

experimentalThe ME ID of the failed step.

SYNTHETIC_TEST_STEP-E3B7B18230E88471

result.failed_step.type

string

experimentalThe type of the failed step.

CLICK

result.failed_step.url

string

experimentalThe URL of the failed step.

https://dynatrace.com

execution.screen_capture MUST be one of the following:

ValueDescription

capture_on_error

Capture on error

capture_on_success

Capture on success

no_capture

No capture

result.failed_step.type MUST be one of the following:

ValueDescription

CLICK

Click

COOKIE

Cookie

JAVASCRIPT

Javascript

KEYSTROKES

Keystrokes

NAVIGATE

Navigate

SELECT_OPTION

Select option

TAP

Tap

Synthetic browser monitor execution result statistics fields

AttributeTypeDescriptionExamples
dt.synthetic_engine.processing.end_timestamptimestampexperimental
The end timestamp of the step/monitor execution as reported by executor.		1629891693487
dt.synthetic_engine.processing.start_timestamptimestampexperimental
The start timestamp of the step/monitor execution as reported by executor.		1529891693487
result.statistics.durationdurationexperimental
The duration of the monitor/step.		456
result.statistics.end_timestamptimestampexperimental
The end timestamp of the execution.		1629891693487
result.statistics.events.countlongexperimental
Number of events reported for this step/monitor.		6
result.statistics.start_timestamptimestampexperimental
The start timestamp of the execution.		1629891693487
result.statistics.transfer_sizelongexperimental
The transfer size of the step/sum of all steps.		678
result.statistics.user_actions.countlongexperimental
Number of user actions reported for this step/monitor.		3
result.statistics.user_actions.durationdurationexperimental
Reported for browser_monitor_execution: Duration of browser monitor, calculated as a sum of all step-level user actions durations. Reported for browser_monitor_step_execution: Duration of individual browser monitor step, measured from the start of the first user action event of the step to the end of the last user action event of the step.		456
result.statistics.user_actions.total_durationdurationexperimental
Reported for browser_monitor_execution: Total duration of browser monitor, measured as a sum of all step-level values of "User actions total duration" metric. Reported for browser_monitor_step_execution: Total duration of individual browser monitor step, measured as a sum of durations of all user actions in the step.		456
result.statistics.user_events.durationdurationexperimental
Reported for browser_monitor_execution: Duration of browser monitor, calculated as a sum of all step-level user events durations. Reported for browser_monitor_step_execution: Duration of individual browser monitor step, measured from the start of the first event of the step to the end of the last event of the step.		456
result.statistics.user_events.total_durationdurationexperimental
Reported for browser_monitor_execution: Total duration of browser monitor, measured as a sum of all step-level values of "User events total duration" metric. Reported for browser_monitor_step_execution: Total duration of individual browser monitor step, measured as a sum of durations of all user events in the step.		456

Synthetic browser monitor step execution

Synthetic browser monitor step execution event

Synthetic base event fields

The following base fields are used for synthetic events.

AttributeTypeDescriptionExamples

timestamp

timestamp

stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created.

1649822520123123123

event.id

string

stableUnique identifier string of an event; is stable across multiple refreshes and updates.

5547782627070661074_1647601320000

event.version

string

stableDescribes the version of the event.

1.0.0

event.type

string

stableThe unique type identifier of a given event.Tags: permission

ESXI_HOST_MEMORY_SATURATION; PROCESS_RESTART; CPU_SATURATION; MEMORY_SATURATION; Automation Workflow; AppEngine Functions - Small

event.kind

string

stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event. 1Tags: permission

SYNTHETIC_EVENT

1

Fixed value SYNTHETIC_EVENT.

Synthetic primary tags fields

The following fields are common for all synthetic events.

AttributeTypeDescriptionExamples

dt.synthetic.monitor.id

string

experimentalThe identifier of the monitor.

HTTP_CHECK-6349B98E1CD87352

dt.entity.synthetic_test

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST.Tags: entity-id

SYNTHETIC_TEST-A140F3B85BCCBD1A

dt.entity.http_check

string

resource stableAn entity ID of an entity of type HTTP_CHECK.Tags: entity-id

HTTP_CHECK-A140F3B85BCCBD1A

dt.entity.multiprotocol_monitor

string

resource stableAn entity ID of an entity of type MULTIPROTOCOL_MONITOR.Tags: entity-id

MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A

dt.entity.external_synthetic_test

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A

monitor.name

string

experimentalThe name of the monitor.

Monitor name

dt.synthetic.step.id

string

experimentalThe identifier of the monitor step.

HTTP_CHECK_STEP-5349B98E1CD87352

dt.entity.synthetic_test_step

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST_STEP.Tags: entity-id

SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

dt.entity.http_check_step

string

resource stableAn entity ID of an entity of type HTTP_CHECK_STEP.Tags: entity-id

HTTP_CHECK_STEP-A140F3B85BCCBD1A

dt.entity.external_synthetic_test_step

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

step.name

string

experimentalThe name of the step.

Step name

step.sequence_number

long

experimentalThe sequence number of the step (numbered from 0).

0

dt.synthetic.monitored_entity_ids

array

experimentalIDs of monitored entities.

APPLICATION-EA7C4B59F27D43EB

primary_tags.__key__

string

experimentalUser-defined primary grail tags, __key__ prefixed with primary_tags.. The value is a string.

tag-value; value

dt.security_context

string

resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: permission

Synthetic execution event fields

The following base fields are used for synthetic execution events.

AttributeTypeDescriptionExamples

execution.type

string

experimentalThe type of the execution.

on-demand

execution.end_timestamp

timestamp

experimentalThe timestamp when execution was finished, in UTC milliseconds.

1629891695487

dt.synthetic.batch.id

long

experimentalThe identifier of the batch (defined for on-demand executions only).

dt.entity.synthetic_location

string

resource stableAn entity ID of an entity of type SYNTHETIC_LOCATION.Tags: entity-id

SYNTHETIC_LOCATION-D140F3B85BCCBD1A

execution.type MUST be one of the following:

ValueDescription

on-creation

on-creation

on-demand

on-demand

on-demand with customized script

on-demand with customized script

on-update

on-update

re-run

re-run

standard

standard

Synthetic step result fields

The following result fields are used for synthetic monitor step execution events.

AttributeTypeDescriptionExamples

result.state

string

experimentalResult state of monitor execution.

FAIL

result.state MUST be one of the following:

ValueDescription

FAIL

Fail

SUCCESS

Success

Synthetic result status fields

The following status fields are used for synthetic execution events.

AttributeTypeDescriptionExamples

result.status.details

string

experimentalStatus details.

connection timed out after 5000 ms: google.com

result.status.on_demand.message

string

experimentalThe on-demand status message.

Success

result.status.on_demand.details

string

experimentalThe details of the status.

PERFORMANCE_THRESHOLD_VIOLATION

result.status.category

string

experimentalThe category of the status.

FAIL

result.status.code

long

experimentalNumeric representation of the status.

599

result.status.message

string

experimentalThe message returned by an execution or a status message.

TIMEOUT

result.status.category MUST be one of the following:

ValueDescription

FAIL

Execution fail

NOT_EXECUTED

Not executed

SUCCESS

Success

UNEXPECTED_ERROR

Unexpected error

Synthetic browser monitor step execution fields

AttributeTypeDescriptionExamples

screenshot.regular_uri

string

experimentalThe screenshot URI of the step.

screenshot.thumbnail_uri

string

experimentalThe screenshot thumbnail URI of the step.

step.type

string

experimentalType of the step.

CLICK

step.url

string

experimentalThe URL of the step.

https://dynatrace.com

step.type MUST be one of the following:

ValueDescription

CLICK

Click

COOKIE

Cookie

JAVASCRIPT

Javascript

KEYSTROKES

Keystrokes

NAVIGATE

Navigate

SELECT_OPTION

Select option

TAP

Tap

Synthetic browser monitor step execution result statistics fields

AttributeTypeDescriptionExamples
dt.synthetic_engine.processing.end_timestamptimestampexperimental
The end timestamp of the step/monitor execution as reported by executor.		1629891693487
dt.synthetic_engine.processing.start_timestamptimestampexperimental
The start timestamp of the step/monitor execution as reported by executor.		1529891693487
result.statistics.durationdurationexperimental
The duration of the monitor/step.		456
result.statistics.end_timestamptimestampexperimental
The end timestamp of the execution.		1629891693487
result.statistics.events.countlongexperimental
Number of events reported for this step/monitor.		6
result.statistics.start_timestamptimestampexperimental
The start timestamp of the execution.		1629891693487
result.statistics.user_actions.countlongexperimental
Number of user actions reported for this step/monitor.		3
result.statistics.user_actions.durationdurationexperimental
Reported for browser_monitor_execution: Duration of browser monitor, calculated as a sum of all step-level user actions durations. Reported for browser_monitor_step_execution: Duration of individual browser monitor step, measured from the start of the first user action event of the step to the end of the last user action event of the step.		456
result.statistics.user_actions.total_durationdurationexperimental
Reported for browser_monitor_execution: Total duration of browser monitor, measured as a sum of all step-level values of "User actions total duration" metric. Reported for browser_monitor_step_execution: Total duration of individual browser monitor step, measured as a sum of durations of all user actions in the step.		456
result.statistics.user_events.durationdurationexperimental
Reported for browser_monitor_execution: Duration of browser monitor, calculated as a sum of all step-level user events durations. Reported for browser_monitor_step_execution: Duration of individual browser monitor step, measured from the start of the first event of the step to the end of the last event of the step.		456
result.statistics.user_events.total_durationdurationexperimental
Reported for browser_monitor_execution: Total duration of browser monitor, measured as a sum of all step-level values of "User events total duration" metric. Reported for browser_monitor_step_execution: Total duration of individual browser monitor step, measured as a sum of durations of all user events in the step.		456
Related tags
Digital Experience