You can collect diagnostic data for an ActiveGate to troubleshoot ActiveGate issues and to give Dynatrace Support the details they need to diagnose the issue.
To collect diagnostic data in the web UI, use the Fleet Management Support Archives feature.
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.
agctl ActiveGate version 1.333+
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 interface tool to collect all the necessary data and create a package that can be analyzed later.
For more information about agctl, see agctl - Command-line interface for ActiveGate.
agctl support-archive commandUse the agctl support-archive command to generate a support archive containing diagnostic data.
For details on the support-archive command, see Support archive.
To collect diagnostic data, run the support-archive command with the create operation.
agctl support-archive create [--directory=<PATH> --days=<NUMBER> --modules=<MODULES> --stdout]
--directory=<PATH> parameter.agctl prints the path to this file.--days=<NUMBER> parameter.--modules=<MODULES> parameter with a comma-separated list of modules (for example, --modules=zremote,synthetic).agctl support-archive command from containerized ActiveGateYou can use support-archive command to gather diagnostic data from a containerized ActiveGate using the --stdout parameter, which outputs the support archive directly and allows you to redirect it to a file on your local machine.
kubectl exec -n <namespace> <pod-name> -- agctl support-archive create --stdout 1 > ag-support-archive.zip 2 > output-logs.txt
The contents of the support archive are written to stdout, allowing them to be redirected to a ZIP file. Other output is sent to stderr to maintain the integrity of the archive file.
Make sure to use the command prompt (cmd.exe) on Windows; PowerShell isn't supported.
agctl for earlier versionsActiveGate version 1.331 and earlier
For earlier versions of ActiveGate, use agctl with the deprecated create-support-archive command to collect diagnostic data.
agctl create-support-archive command on Linux or Windowsagctl is located in ActiveGate install directory.
If you installed ActiveGate in a custom folder, the path to agctl will be different.
agctl must be run with the same user as the ActiveGate process (by default, dtuserag).
Syntax
To collect diagnostic data, run agctl with the create-support-archive command.
sudo -u dtuserag /opt/dynatrace/gateway/agctl create-support-archive [--directory=<PATH> --days=<NUMBER> --modules=<MODULES>]
--directory=<PATH> parameter.agctl prints the path to this file.dtuserag has write permission to the target directory.--days=<NUMBER> parameter.--modules=<MODULES> parameter with a comma-separated list of modules (for example, --modules=zremote,synthetic).agctl create-support-archive command from containerized ActiveGateActiveGate version 1.325+
You can use the --stdout parameter, which outputs the support archive directly and allows you to redirect it to a file on your local machine.
kubectl exec -n <namespace> <pod-name> -- /opt/dynatrace/gateway/agctl create-support-archive --stdout 1 > ag-support-archive.zip 2 > output-logs.txt
The contents of the support archive are written to stdout, allowing them to be redirected to a ZIP file. Other output is sent to stderr to maintain the integrity of the archive file.
Make sure to use the command prompt (cmd.exe) on Windows; PowerShell isn't supported.
ActiveGate version 1.323 and earlier
For earlier versions of containerized ActiveGate, use agctl with the --directory parameter and then transfer the file using base64 encoding.
--days=<days> parameter.--modules=<modules-list> parameter with a comma-separated list of modules (for example, --modules=zremote,synthetic).Run the command.
kubectl exec <pod-name> -n <namespace> -- /opt/dynatrace/gateway/agctl create-support-archive --directory=<tmp-path> [--days=<days> --modules=<modules-list>]
Move the created file to the host. Use base64 to create an encoded file.
kubectl exec <pod-name> -n <namespace> -- base64 --wrap=0 <created-file-path> > <encoded-file-host-path>
Decode the encoded file using the appropriate Windows or Linux command.
base64 --decode -i <encoded-file-path> > <decoded-file-path>
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 |
|---|---|
| Contains general information on when and where the diagnostic data was collected and archive statistics. |
| Contains a snapshot of the ActiveGate configuration directory. |
| Contains a snapshot of the internal environment configuration related to the ActiveGate. |
| Contains a snapshot of the ActiveGate log directory. |
| Contains AutoUpdater service logs and RPM, Synthetic, zRemote installer modules. |
| Contains ActiveGate installer logs. |
| Contains zRemote, watchdog logs and agent configuration files. |
| Contains ActiveGate Synthetic monitors configuration files and logs. |
| Contains logs for Extensions and agent executing them. |