The parameters.configuration when set to true will include the Artifactory configuration files in the support bundle. Some of the notable files include: logback.xml, system.yaml, artifactory.repository.config.json (starting from 7.49.X repositories and their configurations in your Artifactory instance are located in this file instead of the artifactory.config.xml file), artifactory.config.xml, binarystore.xml, artifactory.system.properties, etc. Configuration files for other microservices will also be included. For example, the logback.xml for the Access microservice and the Mission Control microservice (if you have it enabled as microservice) will be placed in the respective folder in the support bundle.
The parameters.system when set to true, will include the storage summary and system information of the instances.
These two configurations do cause the support bundle to take a bit longer since it collects some of this information from the database and the system. If these two sets of information are not needed, consider setting these parameters to false so that your support bundle generation can be faster.
The parameters.logs parameter will collect and bundle the logs from the log directory of Artifactory. You can specify the start and end date in the “YYYY-MM-DD” format. Keep in mind that it will bundle the logs from the log’s archived directory. This means that if the logs have already rotated out and were cleaned up (a.k.a. no longer in the archived directory) even if you placed a date that spans 1 week you may only get logs from a few days back since those logs no longer exist locally.
The thread_dump configurations cause thread dump/s to be generated at support bundle generation. This can cause a delay in support bundle generation depending on how many thread dumps you set as the “count”. If you set more than 1 there will be a delay according to the set “interval”. For example, if you set the “interval” to 15000 (15 seconds) after one thread dump finishes it will wait 15 seconds before triggering another thread dump. This continues until the number of thread dumps set in the count completes.
The parameters.system when set to true, will include the storage summary and system information of the instances.
These two configurations do cause the support bundle to take a bit longer since it collects some of this information from the database and the system. If these two sets of information are not needed, consider setting these parameters to false so that your support bundle generation can be faster.
The parameters.logs parameter will collect and bundle the logs from the log directory of Artifactory. You can specify the start and end date in the “YYYY-MM-DD” format. Keep in mind that it will bundle the logs from the log’s archived directory. This means that if the logs have already rotated out and were cleaned up (a.k.a. no longer in the archived directory) even if you placed a date that spans 1 week you may only get logs from a few days back since those logs no longer exist locally.
The thread_dump configurations cause thread dump/s to be generated at support bundle generation. This can cause a delay in support bundle generation depending on how many thread dumps you set as the “count”. If you set more than 1 there will be a delay according to the set “interval”. For example, if you set the “interval” to 15000 (15 seconds) after one thread dump finishes it will wait 15 seconds before triggering another thread dump. This continues until the number of thread dumps set in the count completes.