Diagnostics Package
Diagnostics Package
A diagnostics package is one .tar.gz archive that contains what Radiator support typically needs
to investigate a problem:
- The active configuration
- All in-memory application and AAA logs
- A summary of the server, its build, resource use, and licenses
The package is not sanitized. It includes private keys, license keys, management credentials, and log rows that can contain user names, attributes, and other user data. Radiator Server does not remove or mask any of these values.
Creating a Package
Radiator UI offers the package download to users with the read privilege. It can also be downloaded
with the Management API, which requires the same privilege:
curl -u admin:password -OJ http://localhost:8080/api/v1/diagnostics/package
The file name has the form radiator-diagnostics-<server-id>-<UTC timestamp>.tar.gz, for example
radiator-diagnostics-C01-R00-2026-10-06T10-00-00Z.tar.gz. The server identifier is the cluster
and instance identifier described in
High Availability Identifiers.
Privileges
Creating a package requires the read privilege or higher. The package contains configuration
files, which require read, and logs, which require monitor. Because read includes all
monitor privileges, a read user can download the complete package. A monitor user receives
HTTP status 403. See Management API Privileges.
Package Contents
| Path | Content |
|---|---|
configuration/ | Active configuration directory |
logs/application.jsonl | Application log rows retained in memory |
logs/aaa/<logger-name>.jsonl | Rows retained in memory for each AAA logger with a memory target |
summary.json | Server, build, resource use, and license summary |
Configuration
The configuration/ folder contains the active configuration directory. Pending changes are not
included. All content directories are included, such as tls/, licenses/, management/, db/,
lua/, templates/, and ui-settings/.
The same entries are excluded as in a configuration export: the internal pending/ and backups/
directories, snapshot and archive metadata, and files and directories whose names begin with ..
See Configuration Import and Export.
Each archive entry keeps the original modification time, permissions, and numeric owner and group.
The archive also records the owner and group names when Radiator Server can resolve them. List them
with tar:
tar -tvzf radiator-diagnostics-R00-2026-10-06T10-00-00Z.tar.gz
Active SQLite databases are copied as consistent snapshots, in the same way as in a configuration export.
Logs
Log files use the JSON Lines format: each line is one log row. The rows are in the order in which
Radiator Server retained them, oldest first. Each row has the same rowId, timestamp, and
fields properties as the JSON log export in Radiator UI.
The package contains only the rows held in memory. The number of rows depends on the size of each
memory logger target. AAA loggers without a memory target
have no file in the package. Log files written to disk and syslog are not included.
In AAA log file names, characters other than letters, digits, -, _, and . are replaced with
_. A name that begins with . gets a _ prefix.
Summary
summary.json contains:
createdAtandcreatedBy: the creation time and the management user who downloaded the packageserver: the server identifier, host name, operating system, and uptime in secondsbuild: the Radiator Server version and build detailsosStats: process and system resource use at creation timelicensesandlicenseStatus: license key details and licensed services, without the keys themselvescollectionErrors: summary parts that Radiator Server could not collect, with the reason
Size and Errors
Radiator Server creates the package in memory before sending it. Large db/ directories and large
memory log buffers increase the package size and the time needed to create it.
If Radiator Server cannot create the package, for example because it cannot read a configuration file, the response contains an error message that names the cause. Radiator UI shows this message.