Diagnostic data startup parameters
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
You can tailor your diagnostic data collection from startup, with the parameters defined in the table that follows.
| Parameter | Description | For more information, see... |
|---|---|---|
Diagnostic directory (-diagDir) |
Specify the directory where the diagnostic tracking log file is written and subdirectories for each diagnostic event are created. | Diagnostic directory (-diagDir) |
Diagnostic events value (-diagEvent) |
Specify the database events to collect diagnostic data for. | Diagnostic events value (-diagEvent) |
Diagnostic event level (-diagEvtLevel) |
Specify the "level" of diagnostic data to collect. | Diagnostic event level (-diagEvtLevel) |
Diagnostic data format (-diagFormat) |
Specify the format of the diagnostic data files. | Diagnostic data format (-diagFormat) |
Diagnostic frequency(-diagFrequency) |
Specify the duration or interval (in number of seconds) to limit the frequency of reporting the subsequent diagnostic events of the same type. | Diagnostic frequency (-diagFrequency) |
Diagnostic field separator (-diagFS) |
Specify the separator to use when writing diagnostic data to a CSV-formatted file. | Diagnostic field separator (-diagFS) |
Diagnostic pause length (-diagPause) |
Specify the number of seconds to pause after recording data for a diagnostic event before processing the event. | Diagnostic pause length (-diagPause) |
Diagnostic prefix value (-diagPrefix) |
Specify a common prefix to standard diagnostic data files. | Diagnostic prefix value (-diagPrefix) |
Diagnostic process (-diagProc) |
Specify an executable to spawn when a diagnostic event triggers. | Diagnostic process (-diagProc) |
Top diagnostic event triggers(-diagTopN) |
Specify the number of most prominent event triggers (offenders) causing a diagnostic event for which diagnostic data must be reported. | Top diagnostic event triggers (-diagTopN) |