You can run fully automated ActiveGate troubleshooting for Dynatrace SaaS and Managed environments.
The workflow enables you to:
If ActiveGate can't connect to the Dynatrace environment or doesn't start, you might need to collect diagnostic data locally from the command line. For details, see Collect diagnostic data with agctl.
This procedure describes the default procedure: Dynatrace collects diagnostics data for an ActiveGate and immediately analyzes it.
If you prefer to collect and review the data before manually submitting it to Dynatrace for analysis, see Collect and review locally.
Go to Deployment Status > ActiveGates.
Expand the ActiveGate entry you want to troubleshoot and select Run ActiveGate diagnostics.
On the Run Dynatrace ActiveGate diagnostics page, briefly describe what isn’t working as expected from your point of view.
optional By default, 7 days of data is collected for analysis. If you need more data, select the Advanced options link, change the number of days, and select Apply.
Select Start analysis.
Dynatrace does the following:
The State column describes the current phase of the process.
State does not automatically refresh. Select Refresh to check for a state change.
Data collection is in progress. While collecting data, you can:
Dynatrace has finished collecting diagnostic data. After collecting data, you can:
Diagnostic data is being transferred to Dynatrace for analysis. While sending data, you can:
Diagnostic data has been transferred to Dynatrace for analysis.
Dynatrace is now analyzing the diagnostic data.
While analyzing data, you can:
The analysis is done. The number of associated alerts is shown in parentheses.
After an analysis, you can:
The diagnostic data is being deleted. While deleting data, you can:
The diagnostic data has been deleted. Dynatrace keeps only a small set of information about who, when, where, and why the diagnostic data was collected.
The diagnostics process was canceled manually before it was finished.
When the analysis is complete, Dynatrace sends the results back to your environment. If a potential solution is identified, Dynatrace lists it in the Alerts section.
This procedure describes how to collect diagnostics data for the ActiveGate. Use this option if you prefer to collect and review the data before manually submitting it to Dynatrace for analysis.
If you instead want to collect data and submit it to Dynatrace automatically for analysis, see Analyze automatically.
Go to Deployment Status > ActiveGates.
Expand the ActiveGate entry you want to troubleshoot and select Run ActiveGate diagnostics.
On the Run Dynatrace ActiveGate diagnostics page, briefly describe what isn’t working as expected from your point of view.
Select the Advanced options link.
Select and store locally.
7 days).Select Apply.
Select Start collection to collect diagnostic data and store it locally.
Dynatrace now:
The State column describes the current phase of the process.
State does not automatically refresh. Select Refresh to check for a state change.
Data collection is in progress. While collecting data, you can:
Dynatrace has finished collecting diagnostic data. After collecting data, you can:
Now that the data is collected, you can:
In a Dynatrace Managed air-gapped environment:
Stringent data privacy protections are enforced and logged throughout this process.
agctl ActiveGate version 1.275+
In cases where ActiveGate cannot connect to the Dynatrace environment or doesn't start, you might need to collect diagnostic data locally from the command line on the ActiveGate host. To do so, use the agctl command line tool to collect all the necessary data and create a package that can be analyzed later.
agctl on Linux or Windowsagctl from containerized ActiveGateYou can use agctl to gather diagnostic data from a containerized ActiveGate. To do so, run the following script and provide the --directory=<path> parameter with the path to your tmp folder.
--days=<days> parameter.--modules=<modules-list> parameter with a comma-separated list of modules (for example, --modules=zremote,synthetic).Decode the encoded file using the appropriate Windows or Linux command.
Now that the data is collected:
We recommend that you delete the file after use.
All the collected diagnostic data is compressed into a SupportArchive<ID number> (for agctl - support_archive_<timestamp>) ZIP file that includes the following folders and files:
Folder or file
Description
details.txt (file)
Contains general information on when and where the diagnostic data was collected and archive statistics.
config (folder)
Contains a snapshot of the ActiveGate configuration directory.
debugui (folder)
Contains a snapshot of the internal environment configuration related to the ActiveGate.
log (folder)
Contains a snapshot of the ActiveGate log directory.
autoupdater (folder)
Contains AutoUpdater service logs and RPM, Synthetic, zRemote installer modules.
install (folder)
Contains ActiveGate installer logs.
zremote (folder)
Contains zRemote, watchdog logs and agent configuration files.
synthetic (folder)
Contains ActiveGate Synthetic monitors configuration files and logs.
remotepluginmodule (folder)
Contains logs for Extensions and agent executing them.
To comply with regional data protection and privacy regulations, Dynatrace automatically deletes all diagnostic data 30 days after its collection. This applies to the data in your Dynatrace environment and on the Dynatrace Cluster.
You can choose to delete collected diagnostic data earlier. To ensure transparency, Dynatrace keeps only a small set of information about who, when, where, and why the diagnostic data was collected.
For related details on Dynatrace data privacy, see Data retention periods.
No, you cannot access the S3 directly or use your own.
The diagnostic data is uploaded to the Dynatrace S3 bucket that is configured for the environment/cluster by Dynatrace. The S3 bucket used depends on the location of the environment/cluster.