Extracting data mart to file
You can create your own data mart extractions to CSV file, for export to a destination host.
About this task
Data mart file names must follow Linux rules. For example,
the file name can't include $
because Linux does not support it. If you create a
file with the name my$file
, the saved file name is my
.
Data
mart file names must follow Linux rules for naming files. For example, file names can't include "$'
since Linux doesn't support it. If you try to create a file named my$file
, the
saved file name is my
.
You can track the extraction and see the overall data mart status in the pre-defined Datamart Extraction Log report.
The data mart configuration commands are run only once per central manager, since all collectors can then receive this information from the central manager.
Bundled data marts: You can bundle a number of CSV export data marts together, both user-defined and pre-defined. Each bundle has a main data mart. Each data mart that is included in a bundle pulls out data based on its own scheduling. After the main data mart extracts data, it puts data files from all the data marts included in the bundle into the one tar file, and sends it to a destination server. The main data mart must have the latest scheduled extraction time of all the data marts in the bundle so that it can include all the other data marts' latest extracts. See datamart_copy_file_bundle.
- Classification, discovered instances, outliers, vulnerability assessment: on the units where these processes are enabled or scheduled.
- Exceptions, groups, system information, unit utilization levels: all units.
- Access, policy violations, S-TAP status: collectors only.
- Datasources, users: central manager, standalone.