Definition of Synthetic events.
Synthetic HTTP monitor execution event
The following base fields are used for synthetic events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
timestamp | timestamp | stable The 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 | stable Unique identifier string of an event; is stable across multiple refreshes and updates. | 5547782627070661074_1647601320000 |
event.version | string | stable Describes the version of the event. | 1.0.0 |
event.type | string | stable The 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 | stable Gives 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. 1 Tags: permission | SYNTHETIC_EVENT |
dt.security_context | string | resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: permission |
Fixed value SYNTHETIC_EVENT.
The following base fields are used for synthetic execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
execution.type | string | experimental The type of the execution. | on-demand |
execution.end_timestamp | timestamp | experimental The timestamp when execution was finished, in UTC milliseconds. | 1629891695487 |
dt.synthetic.batch.id | long | experimental The identifier of the batch (defined for on-demand executions only). | |
dt.synthetic.monitor.id | string | experimental The identifier of the monitor. | HTTP_CHECK-6349B98E1CD87352 |
dt.synthetic.monitored_entity_ids | array | experimental IDs of monitored entities. | APPLICATION-EA7C4B59F27D43EB |
dt.entity.synthetic_location | string | resource stable An entity ID of an entity of type SYNTHETIC_LOCATION. Tags: entity-id | SYNTHETIC_LOCATION-D140F3B85BCCBD1A |
Fixed value SYNTHETIC_EVENT.
The following status fields are used for synthetic execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
result.status.details | string | experimental Status details. | connection timed out after 5000 ms: google.com |
result.status.on_demand.message | string | experimental The on-demand status message. | Success |
result.status.on_demand.details | string | experimental The details of the status. | PERFORMANCE_THRESHOLD_VIOLATION |
result.status.category | string | experimental The category of the status. | FAIL |
result.status.code | long | experimental Numeric representation of the status. | 599 |
result.status.message | string | experimental The message returned by an execution or a status message. | TIMEOUT |
Fixed value SYNTHETIC_EVENT.
The following result fields are used for synthetic monitor execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
result.failed_step.name | string | experimental The name of the failed step | Second step |
result.failed_step.sequence_id | long | deprecated The sequence ID of the step. Replaced by result.failed_step.sequence_number | 2 |
result.failed_step.sequence_number | long | experimental The sequence id of the step. | 2 |
result.executed_steps_count | long | experimental The number of executed steps. | 2 |
result.engine.id | long | experimental The id of the engine which has executed the monitor. | 123 |
result.location.type | string | experimental The type of synthetic location. | private |
result.state | string | experimental Result state of monitor execution. | FAIL |
Fixed value SYNTHETIC_EVENT.
| Attribute | Type | Description | Examples |
|---|---|---|---|
dt.entity.http_check | string | resource stable An entity ID of an entity of type HTTP_CHECK. Tags: entity-id | HTTP_CHECK-A140F3B85BCCBD1A |
| Attribute | Type | Description | Examples |
|---|---|---|---|
result.statistics.duration | duration | experimental The duration of the monitor/step. | 456 |
result.statistics.host_name_resolution_time | long | experimental The host name resolution time of the step/sum of all steps. | 12345 |
result.statistics.peer_certificate_expiry_date | long | experimental The peer certificate expiration date. | 1741996799000 |
result.statistics.redirection_time | long | experimental The redirection time of the step/sum of all steps. | 2 |
result.statistics.redirects_count | long | experimental The number of redirects of the step/sum of all steps. | 266 |
result.statistics.response_body_size_limit_exceeded | boolean | experimental Set to true in case response body size has been exceeded. | true |
result.statistics.response_size | long | experimental The response size of the step/sum of all steps. | 456 |
result.statistics.response_status_code | long | experimental The HTTP status code reported for the execution. | 404 |
result.statistics.start_timestamp | timestamp | experimental The start timestamp of the execution. | 1629891693487 |
result.statistics.tcp_connect_time | long | experimental The tcp connection time of the step/sum of all steps. | 12345 |
result.statistics.time_to_first_byte | long | experimental The time taken until the first byte of the response is received from the server, relevant application caches, or a local resource. Reported for monitor level, calculated for the sum of all steps. | 244 |
result.statistics.tls_handshake_time | long | experimental The tls handshake time of the step/sum of all steps. | 12345 |
Synthetic HTTP step execution event
The following base fields are used for synthetic events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
timestamp | timestamp | stable The 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 | stable Unique identifier string of an event; is stable across multiple refreshes and updates. | 5547782627070661074_1647601320000 |
event.version | string | stable Describes the version of the event. | 1.0.0 |
event.type | string | stable The 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 | stable Gives 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. 1 Tags: permission | SYNTHETIC_EVENT |
dt.security_context | string | resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: permission |
Fixed value SYNTHETIC_EVENT.
The following base fields are used for synthetic execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
execution.type | string | experimental The type of the execution. | on-demand |
execution.end_timestamp | timestamp | experimental The timestamp when execution was finished, in UTC milliseconds. | 1629891695487 |
dt.synthetic.batch.id | long | experimental The identifier of the batch (defined for on-demand executions only). | |
dt.synthetic.monitor.id | string | experimental The identifier of the monitor. | HTTP_CHECK-6349B98E1CD87352 |
dt.synthetic.monitored_entity_ids | array | experimental IDs of monitored entities. | APPLICATION-EA7C4B59F27D43EB |
dt.entity.synthetic_location | string | resource stable An entity ID of an entity of type SYNTHETIC_LOCATION. Tags: entity-id | SYNTHETIC_LOCATION-D140F3B85BCCBD1A |
Fixed value SYNTHETIC_EVENT.
The following result fields are used for synthetic monitor step execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
step.name | string | experimental The name of the step. | Step name |
step.sequence_number | long | experimental The sequence number of the step (numbered from 0). | 0 |
result.state | string | experimental Result state of monitor execution. | FAIL |
Fixed value SYNTHETIC_EVENT.
The following status fields are used for synthetic execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
result.status.details | string | experimental Status details. | connection timed out after 5000 ms: google.com |
result.status.on_demand.message | string | experimental The on-demand status message. | Success |
result.status.on_demand.details | string | experimental The details of the status. | PERFORMANCE_THRESHOLD_VIOLATION |
result.status.category | string | experimental The category of the status. | FAIL |
result.status.code | long | experimental Numeric representation of the status. | 599 |
result.status.message | string | experimental The message returned by an execution or a status message. | TIMEOUT |
Fixed value SYNTHETIC_EVENT.
| Attribute | Type | Description | Examples |
|---|---|---|---|
dt.entity.http_check | string | resource stable An entity ID of an entity of type HTTP_CHECK. Tags: entity-id | HTTP_CHECK-A140F3B85BCCBD1A |
dt.entity.http_check_step | string | resource stable An entity ID of an entity of type HTTP_CHECK_STEP. Tags: entity-id | HTTP_CHECK_STEP-A140F3B85BCCBD1A |
| Attribute | Type | Description | Examples |
|---|---|---|---|
result.statistics.duration | duration | experimental The duration of the monitor/step. | 456 |
result.statistics.host_name_resolution_time | long | experimental The host name resolution time of the step/sum of all steps. | 12345 |
result.statistics.peer_certificate_expiry_date | long | experimental The peer certificate expiration date. | 1741996799000 |
result.statistics.redirection_time | long | experimental The redirection time of the step/sum of all steps. | 2 |
result.statistics.redirects_count | long | experimental The number of redirects of the step/sum of all steps. | 266 |
result.statistics.response_body_size_limit_exceeded | boolean | experimental Set to true in case response body size has been exceeded. | true |
result.statistics.response_size | long | experimental The response size of the step/sum of all steps. | 456 |
result.statistics.response_status_code | long | experimental The HTTP status code reported for the execution. | 404 |
result.statistics.start_timestamp | timestamp | experimental The start timestamp of the execution. | 1629891693487 |
result.statistics.tcp_connect_time | long | experimental The tcp connection time of the step/sum of all steps. | 12345 |
result.statistics.time_to_first_byte | long | experimental The time taken until the first byte of the response is received from the server, relevant application caches, or a local resource. Reported for monitor level, calculated for the sum of all steps. | 244 |
result.statistics.tls_handshake_time | long | experimental The tls handshake time of the step/sum of all steps. | 12345 |
Synthetic HTTP step execution details event
The following base fields are used for synthetic events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
timestamp | timestamp | stable The 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 | stable Unique identifier string of an event; is stable across multiple refreshes and updates. | 5547782627070661074_1647601320000 |
event.version | string | stable Describes the version of the event. | 1.0.0 |
event.type | string | stable The 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 | stable Gives 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. 1 Tags: permission | SYNTHETIC_EVENT |
dt.security_context | string | resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: permission |
Fixed value SYNTHETIC_EVENT.
The following result fields are used for synthetic monitor step execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
step.name | string | experimental The name of the step. | Step name |
step.sequence_number | long | experimental The sequence number of the step (numbered from 0). | 0 |
result.state | string | experimental Result state of monitor execution. | FAIL |
Fixed value SYNTHETIC_EVENT.
| Attribute | Type | Description | Examples |
|---|---|---|---|
custom_logs | record[] | experimental A collection of custom log lines | |
dt.entity.http_check_step | string | resource stable An entity ID of an entity of type HTTP_CHECK_STEP. Tags: entity-id | HTTP_CHECK_STEP-A140F3B85BCCBD1A |
| Attribute | Type | Description | Examples |
|---|---|---|---|
result.statistics.method | string | experimental HTTP request method. | GET; POST; HEAD |
result.statistics.peer_certificate_details | string | experimental The peer certificate details. | Signature Algorithm: SHA256withRSA |
result.statistics.request.header.__key__ | string | experimental HTTP 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 | experimental The request body. | request body |
result.statistics.resolved_ips | record[] | experimental A collection of resolved ips. | |
result.statistics.response.header.__key__ | string | experimental HTTP 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 | experimental The response body. | response body |
result.statistics.response_message | string | experimental The response message. | OK |
result.statistics.url | string | experimental The HTTP request url. | www.dynatrace.com |
Synthetic batch status event
The following base fields are used for synthetic events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
timestamp | timestamp | stable The 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 | stable Unique identifier string of an event; is stable across multiple refreshes and updates. | 5547782627070661074_1647601320000 |
event.version | string | stable Describes the version of the event. | 1.0.0 |
event.type | string | stable The 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 | stable Gives 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. 1 Tags: permission | SYNTHETIC_EVENT |
dt.security_context | string | resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: permission |
Fixed value SYNTHETIC_EVENT.
| Attribute | Type | Description | Examples |
|---|---|---|---|
batch.status | string | experimental The status of the batch. | Success; Failed |
batch.source | string | experimental The source of the batch. | PUBLIC_API |
configuration.fail_on_performance_issue | boolean | experimental Information whether performance issue validation was enabled. | true |
configuration.fail_on_ssl_warning | boolean | experimental Information whether ssl certificate validation was enabled. | true |
configuration.take_screenshot_on_success | boolean | experimental Information whether the execution should provide a screenshot in case of success. | true |
configuration.processing_mode | string | experimental The execution's processing mode | DISABLE_PROBLEM_DETECTION |
failed_executions | record[] | experimental A collection of failed execution objects. Information about on-demand executions that failed. | |
failed_to_execute | record[] | experimental A collection of failed execution objects. Information about on-demand executions that failed to be executed. | |
triggering_problems | record[] | experimental A collection of triggering problem objects. The details of problems encountered while triggering on-demand executions. | |
metadata.__key__ | string[] | experimental The 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[] | experimental A collection of triggered executions ids. | [[12345, 23456]] |
Fixed value SYNTHETIC_EVENT.
Batch result
| Attribute | Type | Description | Examples |
|---|---|---|---|
batch_result.triggered_count | long | experimental The number of triggered executions within the batch. | 6 |
batch_result.executed_count | long | experimental The number of triggered executions with the result SUCCESS or FAILED. | 5 |
batch_result.failed_count | long | experimental The number of triggered executions with the result FAILED. | 4 |
batch_result.failed_to_execute_count | long | experimental The number of executions that were triggered and not executed because of a problem with the Synthetic engine. | 3 |
batch_result.triggering_problems_count | long | experimental The number of executions that were not triggered due to some problems. | 2 |
batch_result.duration | duration | experimental The duration of the batch execution. | 456 |
batch_result.total_duration | duration | experimental The sum of duration of the sum of all executions in batch. | 1567 |
Fixed value SYNTHETIC_EVENT.
| Attribute | Type | Description | Examples |
|---|---|---|---|
user.id | string | stable Unique 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 event
The following base fields are used for synthetic events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
timestamp | timestamp | stable The 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 | stable Unique identifier string of an event; is stable across multiple refreshes and updates. | 5547782627070661074_1647601320000 |
event.version | string | stable Describes the version of the event. | 1.0.0 |
event.type | string | stable The 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 | stable Gives 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. 1 Tags: permission | SYNTHETIC_EVENT |
dt.security_context | string | resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: permission |
Fixed value SYNTHETIC_EVENT.
The following base fields are used for synthetic execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
execution.type | string | experimental The type of the execution. | on-demand |
execution.end_timestamp | timestamp | experimental The timestamp when execution was finished, in UTC milliseconds. | 1629891695487 |
dt.synthetic.batch.id | long | experimental The identifier of the batch (defined for on-demand executions only). | |
dt.synthetic.monitor.id | string | experimental The identifier of the monitor. | HTTP_CHECK-6349B98E1CD87352 |
dt.synthetic.monitored_entity_ids | array | experimental IDs of monitored entities. | APPLICATION-EA7C4B59F27D43EB |
dt.entity.synthetic_location | string | resource stable An entity ID of an entity of type SYNTHETIC_LOCATION. Tags: entity-id | SYNTHETIC_LOCATION-D140F3B85BCCBD1A |
Fixed value SYNTHETIC_EVENT.
The following status fields are used for synthetic execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
result.status.details | string | experimental Status details. | connection timed out after 5000 ms: google.com |
result.status.on_demand.message | string | experimental The on-demand status message. | Success |
result.status.on_demand.details | string | experimental The details of the status. | PERFORMANCE_THRESHOLD_VIOLATION |
result.status.category | string | experimental The category of the status. | FAIL |
result.status.code | long | experimental Numeric representation of the status. | 599 |
result.status.message | string | experimental The message returned by an execution or a status message. | TIMEOUT |
Fixed value SYNTHETIC_EVENT.
The following result fields are used for synthetic monitor execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
result.failed_step.name | string | experimental The name of the failed step | Second step |
result.failed_step.sequence_id | long | deprecated The sequence ID of the step. Replaced by result.failed_step.sequence_number | 2 |
result.failed_step.sequence_number | long | experimental The sequence id of the step. | 2 |
result.executed_steps_count | long | experimental The number of executed steps. | 2 |
result.engine.id | long | experimental The id of the engine which has executed the monitor. | 123 |
result.location.type | string | experimental The type of synthetic location. | private |
result.state | string | experimental Result state of monitor execution. | FAIL |
Fixed value SYNTHETIC_EVENT.
| Attribute | Type | Description | Examples |
|---|---|---|---|
dt.entity.synthetic_test | string | resource stable An entity ID of an entity of type SYNTHETIC_TEST. Tags: entity-id | SYNTHETIC_TEST-A140F3B85BCCBD1A |
execution.retry_on_error | boolean | experimental Should we ignore this execution attempt (which was a failure) - will there be retry. | true |
execution.screen_capture | string | experimental Screen capture mode | capture_on_error |
next_execution.id | long | experimental Next execution id for sequential mode. | 100681465183 |
reference_execution.id | long | experimental Retried execution's id. | 100681465183 |
execution.screen_capture MUST be one of the following:
| Value | Description |
|---|---|
capture_on_error | Capture on error |
capture_on_success | Capture on success |
no_capture | No capture |
| Attribute | Type | Description | Examples |
|---|---|---|---|
dt.synthetic_engine.processing.end_timestamp | timestamp | experimental The end timestamp of the step/monitor execution as reported by executor. | 1629891693487 |
dt.synthetic_engine.processing.start_timestamp | timestamp | experimental The start timestamp of the step/monitor execution as reported by executor. | 1529891693487 |
result.statistics.duration | duration | experimental The duration of the monitor/step. | 456 |
result.statistics.end_timestamp | timestamp | experimental The end timestamp of the execution. | 1629891693487 |
result.statistics.events_count | long | experimental Number of events reported for this step/monitor. | 6 |
result.statistics.start_timestamp | timestamp | experimental The start timestamp of the execution. | 1629891693487 |
result.statistics.total_duration | duration | experimental Sum of durations for each event in step/sum of all events duration. | 456 |
result.statistics.transfer_size | long | experimental The transfer size of the step/sum of all steps. | 678 |
result.statistics.user_action.total_duration | duration | experimental Sum of user action events durations. | 456 |
result.statistics.user_actions_count | long | experimental Number of user actions reported for this step/monitor. | 3 |
Synthetic browser monitor step execution event
The following base fields are used for synthetic events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
timestamp | timestamp | stable The 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 | stable Unique identifier string of an event; is stable across multiple refreshes and updates. | 5547782627070661074_1647601320000 |
event.version | string | stable Describes the version of the event. | 1.0.0 |
event.type | string | stable The 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 | stable Gives 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. 1 Tags: permission | SYNTHETIC_EVENT |
dt.security_context | string | resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: permission |
Fixed value SYNTHETIC_EVENT.
The following base fields are used for synthetic execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
execution.type | string | experimental The type of the execution. | on-demand |
execution.end_timestamp | timestamp | experimental The timestamp when execution was finished, in UTC milliseconds. | 1629891695487 |
dt.synthetic.batch.id | long | experimental The identifier of the batch (defined for on-demand executions only). | |
dt.synthetic.monitor.id | string | experimental The identifier of the monitor. | HTTP_CHECK-6349B98E1CD87352 |
dt.synthetic.monitored_entity_ids | array | experimental IDs of monitored entities. | APPLICATION-EA7C4B59F27D43EB |
dt.entity.synthetic_location | string | resource stable An entity ID of an entity of type SYNTHETIC_LOCATION. Tags: entity-id | SYNTHETIC_LOCATION-D140F3B85BCCBD1A |
Fixed value SYNTHETIC_EVENT.
The following result fields are used for synthetic monitor step execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
step.name | string | experimental The name of the step. | Step name |
step.sequence_number | long | experimental The sequence number of the step (numbered from 0). | 0 |
result.state | string | experimental Result state of monitor execution. | FAIL |
Fixed value SYNTHETIC_EVENT.
The following status fields are used for synthetic execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
result.status.details | string | experimental Status details. | connection timed out after 5000 ms: google.com |
result.status.on_demand.message | string | experimental The on-demand status message. | Success |
result.status.on_demand.details | string | experimental The details of the status. | PERFORMANCE_THRESHOLD_VIOLATION |
result.status.category | string | experimental The category of the status. | FAIL |
result.status.code | long | experimental Numeric representation of the status. | 599 |
result.status.message | string | experimental The message returned by an execution or a status message. | TIMEOUT |
Fixed value SYNTHETIC_EVENT.
| Attribute | Type | Description | Examples |
|---|---|---|---|
dt.entity.synthetic_test | string | resource stable An entity ID of an entity of type SYNTHETIC_TEST. Tags: entity-id | SYNTHETIC_TEST-A140F3B85BCCBD1A |
dt.entity.synthetic_test_step | string | resource stable An entity ID of an entity of type SYNTHETIC_TEST_STEP. Tags: entity-id | SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A |
screenshot.regular_uri | string | experimental The screenshot URI of the step. | |
screenshot.thumbnail_uri | string | experimental The screenshot thumbnail URI of the step. | |
step.type | string | experimental Type of the step. | CLICK |
step.url | string | experimental The URL of the step. | https://dynatrace.com |
step.type MUST be one of the following:
| Value | Description |
|---|---|
CLICK | Click |
COOKIE | Cookie |
JAVASCRIPT | Javascript |
KEYSTROKES | Keystrokes |
NAVIGATE | Navigate |
SELECT_OPTION | Select option |
TAP | Tap |
| Attribute | Type | Description | Examples |
|---|---|---|---|
dt.synthetic_engine.processing.end_timestamp | timestamp | experimental The end timestamp of the step/monitor execution as reported by executor. | 1629891693487 |
dt.synthetic_engine.processing.start_timestamp | timestamp | experimental The start timestamp of the step/monitor execution as reported by executor. | 1529891693487 |
result.statistics.duration | duration | experimental The duration of the monitor/step. | 456 |
result.statistics.end_timestamp | timestamp | experimental The end timestamp of the execution. | 1629891693487 |
result.statistics.events_count | long | experimental Number of events reported for this step/monitor. | 6 |
result.statistics.start_timestamp | timestamp | experimental The start timestamp of the execution. | 1629891693487 |
result.statistics.total_duration | duration | experimental Sum of durations for each event in step/sum of all events duration. | 456 |
result.statistics.user_action.total_duration | duration | experimental Sum of user action events durations. | 456 |
result.statistics.user_actions_count | long | experimental Number of user actions reported for this step/monitor. | 3 |
Synthetic network availability monitor execution event
The following base fields are used for synthetic events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
timestamp | timestamp | stable The 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 | stable Unique identifier string of an event; is stable across multiple refreshes and updates. | 5547782627070661074_1647601320000 |
event.version | string | stable Describes the version of the event. | 1.0.0 |
event.type | string | stable The 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 | stable Gives 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. 1 Tags: permission | SYNTHETIC_EVENT |
dt.security_context | string | resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: permission |
Fixed value SYNTHETIC_EVENT.
The following base fields are used for synthetic execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
execution.type | string | experimental The type of the execution. | on-demand |
execution.end_timestamp | timestamp | experimental The timestamp when execution was finished, in UTC milliseconds. | 1629891695487 |
dt.synthetic.batch.id | long | experimental The identifier of the batch (defined for on-demand executions only). | |
dt.synthetic.monitor.id | string | experimental The identifier of the monitor. | HTTP_CHECK-6349B98E1CD87352 |
dt.synthetic.monitored_entity_ids | array | experimental IDs of monitored entities. | APPLICATION-EA7C4B59F27D43EB |
dt.entity.synthetic_location | string | resource stable An entity ID of an entity of type SYNTHETIC_LOCATION. Tags: entity-id | SYNTHETIC_LOCATION-D140F3B85BCCBD1A |
Fixed value SYNTHETIC_EVENT.
The following status fields are used for synthetic execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
result.status.details | string | experimental Status details. | connection timed out after 5000 ms: google.com |
result.status.on_demand.message | string | experimental The on-demand status message. | Success |
result.status.on_demand.details | string | experimental The details of the status. | PERFORMANCE_THRESHOLD_VIOLATION |
result.status.category | string | experimental The category of the status. | FAIL |
result.status.code | long | experimental Numeric representation of the status. | 599 |
result.status.message | string | experimental The message returned by an execution or a status message. | TIMEOUT |
Fixed value SYNTHETIC_EVENT.
The following result fields are used for synthetic monitor execution events.
| Attribute | Type | Description | Examples |
|---|---|---|---|
result.failed_step.name | string | experimental The name of the failed step | Second step |
result.failed_step.sequence_id | long | deprecated The sequence ID of the step. Replaced by result.failed_step.sequence_number | 2 |
result.failed_step.sequence_number | long | experimental The sequence id of the step. | 2 |
result.executed_steps_count | long | experimental The number of executed steps. | 2 |
result.engine.id | long | experimental The id of the engine which has executed the monitor. | 123 |
result.location.type | string | experimental The type of synthetic location. | private |
result.state | string | experimental Result state of monitor execution. | FAIL |
Fixed value SYNTHETIC_EVENT.
| Attribute | Type | Description | Examples |
|---|---|---|---|
dt.entity.multiprotocol_monitor | string | resource stable An entity ID of an entity of type MULTIPROTOCOL_MONITOR. Tags: entity-id | MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A |
| Attribute | Type | Description | Examples |
|---|---|---|---|
result.statistics.duration | duration | experimental The duration of the monitor/step. | 456 |
result.statistics.start_timestamp | timestamp | experimental The start timestamp of the execution. | 1629891693487 |