Property files - Documentation for TrueSight Smart Reporting for Server Automation 20.02.01

Property fileIncluded in the default ETL run?Description

RunETL.properties

YesRuns all scenarios.agentlogs.propertiesNo

The default property file, RunETL.properties, does not include a scenario for the agent logs report data group. Agent logs is a unique data group.

You can run data from the agent logs group with the run_etl.nsh script by providing the agentlogs.properties file as the value for the -f argument. When you run the script, the 3_AGENT_LOGS scenario is called after the 1_MASTER, 2_FOUNDATION, and 3_PERMISSION_RBAC scenarios. 

audit.properties

YesThe default property file, RunETL.properties includes a scenario for the audit report data group. You can also run this scenario separately, by providing the audit.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 4_AUDIT scenario is called after the 1_MASTER, 2_FOUNDATION, 3_PERMISSION_RBAC, and scenarios starting with number 3.

compliance.properties

YesThe default property file, RunETL.properties includes a scenario for the compliance report data group. You can also run this scenario separately, by providing the compliance.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 3_COMPLIANCE scenario is called after the 1_MASTER, 2_FOUNDATION, and 3_PERMISSION_RBAC scenarios.

inventory.properties

YesThe default property file, RunETL.properties includes a scenario for the inventory report data group. You can also run this scenario separately, by providing the inventory.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 4_INVENTORY scenario is called after the 1_MASTER, 2_FOUNDATION, 3_PERMISSION_RBAC, and scenarios starting with number 3.

jobactivity.properties

NoThe default property file, RunETL.properties does not include a scenario for the job activity report data group. This is a unique report group. You can also run this scenario separately, by providing the inventory.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 3_JOB_ACTIVITY scenario is called after the 1_MASTER, 2_FOUNDATION, and 3_PERMISSION_RBAC scenarios.

jobrunevent.properties

No

The default property file, RunETL.properties, does not include the scenario for job run events. This is a unique scenario.

You can run the job run event scenario with the run_etl.nsh script by providing the jobrunevent.properties file as the value for the -f argument. When you run the script, the 3_JOB_RUN_EVENT scenario is called after the 1_MASTER, 2_FOUNDATION, and 3_PERMISSION_RBAC scenarios.

jobschedule.properties

YesThe default property file, RunETL.properties, includes the scenario for job schedules. You can also run this scenario separately with the run_etl.nsh script by providing the jobschedule.properties file as the value for the -f argument. When you run the script, the 3_JOB_RUN_SCHEDULE scenario is called after the 1_MASTER, 2_FOUNDATION, and 3_PERMISSION_RBAC scenarios. kpi.propertiesNo

The default property file, RunETL.properties, does not include the scenario for the KPI data group. This is a unique scenario.

You can run the KPI scenario with the run_etl.nsh script by providing the kpi.properties file as the value for the -fargument. When you run the script, the 4_KPI scenario is called after the 0_PREREQCHK and scenarios starting with number 3.

patch.properties

YesThe default property file, RunETL.properties includes a scenario for the patching report data group. You can also run this scenario separately, by providing the patch.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 3_PATCH scenario is called after the 1_MASTER, 2_FOUNDATION, and 3_PERMISSION_RBAC scenarios.

property.properties

YesThe default property file, RunETL.properties includes a scenario for the properties report data group. You can also run this scenario separately, by providing the property.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 3_PROPERTY scenario is called after the 1_MASTER, 2_FOUNDATION, and 3_PERMISSION_RBAC scenarios.

provisioning.properties

YesThe default property file, RunETL.properties includes a scenario for the provisioning report data group. You can also run this scenario separately, by providing the provisioning.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 3_PROVISIONING scenario is called after the 1_MASTER, 2_FOUNDATION, and 3_PERMISSION_RBAC scenarios.

rbac.properties

YesThe default property file, RunETL.properties includes a scenario for the RBAC report data group. You can also run this scenario separately, by providing the rbac.properties file as the value for the -f argument in the run_etl.nsh script. When you run the script, the 3_RBAC scenario is called after the 1_MASTER, 2_FOUNDATION, and 3_PERMISSION_RBAC scenarios.smartgroup.propertiesNo

The default property file, RunETL.properties, does not include the scenario for smart groups. This is a unique scenario.

You can run the smart group scenario with the run_etl.nsh script by providing the smartgroup.properties file as the value for the -f argument. When you run the script, the 3_SMART_GROUP scenario is called after the 1_MASTER, 2_FOUNDATION, and 3_PERMISSION_RBAC scenarios.