20 Mar 2024 02:12 PM - edited 06 Sep 2024 12:57 PM
If you are using a Private Synthetic location you will, at some point, want to check the logs for more information about what you are troubleshooting. This article aims to give you some direction on which logs to look at.
You can also download the Support Archive from the WebUI by running the Dynatrace ActiveGate Diagnostics. This will only give you up to 7 days of Synthetic logs, so if you need a log that was last written before that you will need to find the file directly.
The Synthetic installation log details the installation of the Synthetic module. This is the place to check if you see the Synthetic module update has failed or been skipped. It also provides information on the Chromium autoupdate.
It should be read alongside the Gateway installation log, which is located at:
This log is written to when the VUC service is starting up and contains things like the process id and port being used. It often has helpful messages when the VUC service is failing during startup or has stopped unexpectedly.
This file captures the core VUC functionality logs. It includes logs related to the VUC's connection with the ActiveGate (e.g., localhost:9999/...), as well as startup/shutdown activities, common services, and the loading of configuration properties.
This log provides high-level Browser Monitor module logging and covers the execution and lifecycle of visits. It contains information on screenshot storage, WebSocket issues, and other problems encountered during the start up of the Browser module and execution of Browser monitors. The outcome of the diagnostics test on start up can be found in this log by searching for DIAGNOSTICS TEST
This log file details monitor execution events
This provides high-level HTTP Module logging, including monitor start and stop times, script loading, and detailed error information, such as "Unknown Method Error" and "Unexpected Error". The outcome of the diagnostics test on start up can be found in this log by searching for DIAGNOSTICS TEST
Entries in this log are generated from JavaScript execution. You may find log messages created by the API calls api.info(message), api.warn(message), and api.error(message).
This log file details monitor execution events, including script execution failures, SSL communication errors, DNS query timeouts, and other unexpected errors.
This log file details monitor execution events
This log provides high-level NAM, Multi-protocol, module logging and covers the execution and lifecycle of visits
This log file details monitor execution events
This log offers a summary of each VUC startup, including configuration settings and version information.
Location for individual Browser Monitor execution logs:
For archived logs:
Log File Format: <tenant_id>-<test_def_id>-<visit_id>-<timestamp>-ch.log
Execution logs from logs folder are archived hourly into 1 hour zip files in the archivedLogs folder.
These logs provide details on:
For more Synthetic Troubleshooting articles, please check the https://community.dynatrace.com/t5/Troubleshooting/Synthetic-Troubleshooting-Map/ta-p/250426