Execution
Once we have the configuration file set, we can collect and upload data. The usage for the
command can be shown using the --help
. Running that will display the following:
Below is a description of the main functions.
Collecting Data
Once deployed, you may now run the collect_data
script on each server. The command to
run it is:
This will execute the collection based on the predefined parameters in the configuration file.
For example, lets show a run with the defaults:
The script then will do as follows:
-
Collect all the files from the default directories into a compressed archive.
The archive name have the format:
[hostname]-[ip]-[date]-[time].tar.zst
-
The archive will be stored in the archive output directory
The file will be stored in the archive directory available for uploading.
An example of the compressed archive file:
As we can see in this example, the directory is constructed of the 4 parameters mentioned:
a. Server Name: regatta-host05
b. Internal IP: 172_27_12_2
c. Date: 2024_11_14
d. Time: 15_52_56
Uploading Data
If we would like to upload the data collected from the previous command, we would update the
following parameters in the data_collect_configuration.json
:
As described previously, this will cause the data_collect
script to do as follows:
- Avoid collecting data:
When tar_path is not null, the data will not be collected from the default paths but
rather read from the path in tar_path
.
- Apply the filter:
The data collected from the directory will be filtered according to the templates in
file_ignore_list
.
- Upload
The data will be uploaded to the Regatta cloud storage bucket
Once the data is uploaded, Regatta Support will be able to review and analyze the data.
tar_path
as null
. In this case the data will be collected and uploaded to the Regatta
cloud bucket in a single run.