A. Configuring the basic properties

Some of the basic properties display default values. You can modify these values if required.

To configure the basic properties:

1. In the console, navigate to Administration > ETL & System Tasks, and select ETL tasks.
2. On the ETL tasks page, click Add > Add ETL. The Add ETL page displays the configuration properties. You must configure properties in the following tabs: Run configuration, Entity catalog, and Amazon Web Services Connection
3. On the Run Configuration tab, select Moviri - Dynatrace Extractor from the ETL Module list. The name of the ETL is displayed in the ETL task name field. You can edit this field to customize the name.
   
   
4. Click the Entity catalog tab, and select one of the following options:
   • Shared Entity Catalog:
     • From the Sharing with Entity Catalog list, select the entity catalog name that is shared between ETLs.
   • Private Entity Catalog: Select if this is the only ETL that extracts data from the Dynatrace resources.

5. Click the Dynatrace - Connection Parameters tab, and configure the following properties:

   Property	Description
   API Version	Choose between v1 (SmartScape) or v2 (Monitored Entities)
   Dynatrace URL prefix	Dynatrace URL. The URL must be in the form "https://{id}.live.dynatrace.com"
   Dynatrace API Token	Dynatrace API Token (Generated in the Prerequisite)
   Semi-colon separated list of HTTP Headers (<header>:"<value>")	Extra Http Header key-valye pair used for accessing Dynatrace API (semi-colon separate list for multiple HTTP Headers)
   Use HTTP Proxy to connect to Dynatrace	Select yes if a HTTP proxy is required in order to connect to Dynatrace API
   Use HTTPS	Whether or not use HTTPS to connect to the HTTP(S) proxy.
   HTTP Proxy Address	HTTP Proxy FQDN or IP Address
   HTTP Proxy Port	HTTP(S) proxy server port
   HTTP Proxy Username	HTTP(S) proxy server username
   HTTP Proxy Password	HTTP(S) proxy server password

Click the Dynatrace - Extraction tab, and configure the following properties:

1. Click the Dynatrace - Filter tab, and configure the following properties:

   Property	Description
   Collect infrastructure metrics	If selected, the connector will collect metrics at host level (VM, Generic)
   Import indirect services for each applications	If selected, the indirect services will be imported
   Skip Process Group aggregation	If selected, the processes data won't be aggregated to Services
   Extract service key request metrics	If Selected, the key request metrics (BYSET_* Business Driver Metrics) will be imported
   Extract all hosts	If Selected, all the hosts (even the one not assigned to any application/service) will be imported. Host not assigned to any application will be available in the "Infrastructure" domain
   Extract all services	If Selected, all the services (even the one not assigned to any application) will be imported. Services are not assigned to any application will be available in the "Services" domain
   Extract BYFS_ metrics for hosts?	If Selected, it will import byfs_metrics, which results in a very slow execution since it's not aggregated. Default is "No" If Selected, the Disk's UUID (format DISK-123456789) will be used as sub object names. If want to use disk name (path), manually add a property "extract.dynatrace.disk.name" and set to "true". Extracting Disk names will require to use API V2 Read Entities scope. Please refer to "Generate the token" section above. Using disk name (path) will also results in a slow execution.
   Extract network interface metrics for hosts?	If Selected, it will extract network interfaces from the API and create a map
   Change entitytype based on Cloud type?	Change entity type based on cloud type, limited to aws, gcp, azure, and oracle. Openstack or other vm platform type will be put as "generic".
   Custom metrics JSON file location	The location of where the custom metrics configuration JSON file. If not want to use the custom metrics, leave this field empty.
   Application Allowlist  (; separated)	Semicolon separated list of Java Regular Expression that will be used to identify the applications to be imported (multiple Regular Expressions will be considered in "OR" clause)
   Application Denylist (; separated)	Semicolon separated list of Java Regular Expression that will be used to identify the applications not to be imported (multiple Regular Expressions will be considered in "OR" clause)
   Application Allowlist (; separated), support Application ID	Semicolon separated list of Application ID that will be used to identify the applications to be imported (multiple Regular Expressions will be considered in "OR" clause). This property does not accept Regular Expression, an exact match of the Application ID will be performed.
   Application Denylist (; separated), support Application ID	Semicolon separated list of Application ID that will be used to identify the applications to be imported (multiple Regular Expressions will be considered in "OR" clause). This property does not accept Regular Expression, an exact match of the Application ID will be performed.
   Application Injection Type Allowlist (; separated)	Semicolon separated list of Injection Types to be imported. This property does not accept regular expressions, an exact match of Injection Types will be performed.
   Application Injection Type Denylist (; separated)	Semicolon separated list of Injection Types to not be imported. This property does not accept regular expressions, an exact match of Injection Types will be performed.
   Host Allowlist (; separated)	Semicolon separated list of Java Regular Expression that will be used to identify the hosts to be imported (multiple Regular Expressions will be considered in "OR" clause)
   Host Denylist (; separated)	Semicolon separated list of Java Regular Expression that will be used to identify the hosts not to be imported (multiple Regular Expressions will be considered in "OR" clause)
   Host Allowlist (; separated), support Host ID	Semicolon separated list of Host ID that will be used to identify the applications to be imported (the Regular Expressions will be considered in "OR" statements). This property does not accept Regular Expression, an exact match of the Host ID will be performed.
   Host Denylist (; separated), support Host ID	Semicolon separated list of Host ID that will be used to identify the applications not to be imported (the Regular Expressions will be considered in "OR" statements). This property does not accept Regular Expression, an exact match of the Host ID will be performed.
   Host Monitoring Mode filter Allowlist (; separated)	Semicolon separated list of Host Monitoring Modes to be imported. This property does not accept regular expressions, an exact match of the Host Monitoring Modes will be performed.
   Host Monitoring Mode filter Denylist (; separated)	Semicolon separated list of Host Monitoring Modes to not be imported. This property does not accept regular expressions, an exact match of the Host Monitoring Modes will be performed.
   Host Network Zone filter Allowlist (; separated)	Semicolon separated list of Host Network Zones to be imported. This property does not accept regular expressions, an exact match of the Host Network Zones will be performed.
   Host Network Zone filter Allowlist (; separated)	Semicolon separated list of Host Network Zones to not be imported. This property does not accept regular expressions, an exact match of the Host Network Zones will be performed.
   Host Operating System Type filter Allowlist (; separated)	Semicolon separated list of Host Operating System Types to be imported. This property does not accept regular expressions, an exact match of the Host Operating System Type will be performed.
   Host Operating System Type filter Denylist (; separated)	Semicolon separated list of Host Operating System Types to not be imported. This property does not accept regular expressions, an exact match of the Host Operating System Type will be performed.
   Host State filter Allowlist (; separated)	Semicolon separated list of Host States to be imported. This property does not accept regular expressions, an exact match of the Host States will be performed.
   Host State filter Denylist (; separated)	Semicolon separated list of Host States to not be imported. This property does not accept regular expressions, an exact match of the Host States will be performed.
   Host Hypervisor Type filter Allowlist (; separated)	Semicolon separated list of Host Hypervisor Types to be imported. This property does not accept regular expressions, an exact match of the Host Hypervisor Types will be performed.
   Host Hypervisor Type filter Denylist (; separated)	Semicolon separated list of Host Hypervisor Types to not be imported. This property does not accept regular expressions, an exact match of the Host Hypervisor Types will be performed.
   Service Allowlist (; separated)	Semicolon separated list of Java Regular Expression that will be used to identify the services to be imported (multiple Regular Expressions will be considered in "OR" clause).
   Service Denylist (; separated)	Semicolon separated list of Java Regular Expression that will be used to identify the services not to be imported (multiple Regular Expressions will be considered in "OR" clause).
   Service Allowlist (; separated), support Service ID	Semicolon separated list of Service ID that will be used to identify the applications to be imported (the Regular Expressions will be considered in "OR" statements). This property does not accept Regular Expression, an exact match of the Service ID will be performed.
   Service Denylist (; separated), support Service ID	Semicolon separated list of Service ID that will be used to identify the applications not to be imported (the Regular Expressions will be considered in "OR" statements). This property does not accept Regular Expression, an exact match of the Service ID will be performed.
   Service Software Technology Allowlist (; separated)	Semicolon separated list of Software Technologies to be imported. This property does not accept regular expression, an exact match of the Software Technologies will be performed.
   Service Software Technology Denylist (; separated)	Semicolon separated list of Software Technologies to not be imported. This property does not accept regular expression, an exact match of the Software Technologies will be performed.
   Tags for filtering Apps (; separated)	Semicolon separated list of tags to filter out the applications. Format can be [Context]tag:value or tag:value or tag. All the tags must apply to the in-scope Applications (multiple tags will be considered in "AND" clause)
   Tags for filtering Services (; separated)	Semicolon separated list of tags to filter out the services. Format can be [Context]tag:value or tag:value or tag. All the tags must apply to the in-scope Service (multiple tags will be considered in "AND" clause)
   Tags for filtering Hosts(; separated)	Semicolon separated list of tags to filter out the hosts. Format can be [Context]tag:value or tag:value or tag. All the tags must apply to the in-scope Applications (multiple tags will be considered in "AND" clause)

   File Filter option available.
   An option to add Domain name to lookup value to the infrastructure folder, only there when using business services, is available.

The following image shows sample configuration values for the basic properties.

1. (Optional) Override the default values of properties in the following tabs:

   Run configuration

   Property	Description
   Module selection	Select one of the following options: Based on datasource: This is the default selection. Based on Open ETL template: Select only if you want to collect data that is not supported by BMC Helix Continuous Optimization.
   Module description	A short description of the ETL module.
   Execute in simulation mode	By default, the ETL execution in simulation mode is selected to validate connectivity with the data source, and to ensure that the ETL does not have any configuration issues. In the simulation mode, the ETL does not load data into the database. This option is useful when you want to test a new ETL task. To run the ETL in the production mode, select No. BMC recommends that you run the ETL in the simulation mode after ETL configuration and then run it in the production mode.

   Object relationships

   Property

   Description

   Associate new entities to

   Specify the domain to which you want to add the entities created by the ETL. Select one of the following options: Existing domain: This option is selected by default. Select an existing domain from the Domain list. If the selected domain is already used by other hierarchy rules, select one of the following Domain conflict options: Enrich domain tree: Select to create a new independent hierarchy rule for adding a new set of entities, relations, or both that are not defined by other ETLs. ETL Migration: Select if the new ETL uses the same set of entities, relations, or both that are already defined by other ETLs. New domain: Select a parent domain, and specify a name for your new domain. By default, a new domain with the same ETL name is created for each ETL. When the ETL is created, a new hierarchy rule with the same name of the ETL task is automatically created in the active state. If you specify a different domain for the ETL, the hierarchy rule is updated automatically.

   ETL task properties

   Property	Description
   Task group	Select a task group to classify the ETL.
   Running on scheduler	Select one of the following schedulers for running the ETL: Primary Scheduler: Runs on the Application Server. Generic Scheduler: Runs on a separate computer. Remote: Runs on remote computers.
   Maximum execution time before warning	Indicates the number of hours, minutes, or days for which the ETL must run before generating warnings or alerts, if any.
   Frequency	Select one of the following frequencies to run the ETL: Predefined: This is the default selection. Select a daily, weekly, or monthly frequency, and then select a time to start the ETL run accordingly. Custom: Specify a custom frequency, select an appropriate unit of time, and then specify a day and a time to start the ETL run.

2. Click Save.
   The ETL tasks page shows the details of the newly configured Dynatrace ETL.
   
   

(Optional) B. Configuring the advanced properties

You can configure the advanced properties to change the way the ETL works or to collect additional metrics.

To configure the advanced properties:

1. On the Add ETL page, click Advanced.

2. Configure the following properties:

   Run configuration

   Property	Description
   Run configuration name	Specify the name that you want to assign to this ETL task configuration. The default configuration name is displayed. You can use this name to differentiate between the run configuration settings of ETL tasks.
   Deploy status	Select the deploy status for the ETL task. For example, you can initially select Test and change it to Production after verifying that the ETL run results are as expected.
   Log level	Specify the level of details that you want to include in the ETL log file. Select one of the following options: 1 - Light: Select to add the bare minimum activity logs to the log file. 5 - Medium: Select to add the medium-detailed activity logs to the log file. 10 - Verbose: Select to add detailed activity logs to the log file. Use log level 5 as a general practice. You can select log level 10 for debugging and troubleshooting purposes.
   Datasets	Specify the datasets that you want to add to the ETL run configuration. The ETL collects data of metrics that are associated with these datasets. Click Edit. Select one (click) or more (shift+click) datasets from the Available datasets list and click >> to move them to the Selected datasets list. Click Apply. The ETL collects data of metrics associated with the datasets that are available in the Selected datasets list.

   Collection level

   Property	Description
   Metric profile selection	Select the metric profile that the ETL must use. The ETL collects data for the group of metrics that is defined by the selected metric profile. Use Global metric profile: This is selected by default. All the out-of-the-box ETLs use this profile. Select a custom metric profile: Select the custom profile that you want to use from the Custom metric profile list. This list displays all the custom profiles that you have created.
   Levels up to	Specify the metric level that defines the number of metrics that can be imported into the database. The load on the database increases or decreases depending on the selected metric level.

   Loader configuration

   Property	Description
   Empty dataset behavior	Specify the action for the loader if it encounters an empty dataset: Warn: Generate a warning about loading an empty dataset. Ignore: Ignore the empty dataset and continue parsing.
   ETL log file name	The name of the file that contains the ETL run log. The default value is: %BASE/log/%AYEAR%AMONTH%ADAY%AHOUR%MINUTE%TASKID
   Maximum number of rows for CSV output	A numeric value to limit the size of the output files.
   CSV loader output file name	The name of the file that is generated by the CSV loader. The default value is: %BASE/output/%DSNAME%AYEAR%AMONTH%ADAY%AHOUR%ZPROG%DSID%TASKID
   Capacity Optimization loader output file name	The name of the file that is generated by the BMC Helix Continuous Optimization Capacity Optimization loader. The default value is: %BASE/output/%DSNAME%AYEAR%AMONTH%ADAY%AHOUR%ZPROG%DSID%TASKID
   Detail mode	Specify whether you want to collect raw data in addition to the standard data. Select one of the following options: Standard: Data will be stored in the database in different tables at the following time granularities: Detail (configurable, by default: 5 minutes), Hourly, Daily, and Monthly. Raw also: Data will be stored in the database in different tables at the following time granularities: Raw (as available from the original data source), Detail (configurable, by default: 5 minutes), Hourly, Daily, and Monthly. Raw only: Data will be stored in the database in a table only at Raw granularity (as available from the original data source).
   Remove domain suffix from datasource name (Only for systems)	Select True to remove the domain from the data source name. For example, server.domain.com will be saved as server. The default selection is False.
   Leave domain suffix to system name (Only for systems)	Select True to keep the domain in the system name. For example: server.domain.com will be saved as is. The default selection is False.
   Update grouping object definition (Only for systems)	Select True if you want the ETL to update the grouping object definition for a metric that is loaded by the ETL. The default selection is False.
   Skip entity creation (Only for ETL tasks sharing lookup with other tasks)	Select True if you do not want this ETL to create an entity and discard data from its data source for entities not found in Capacity Optimization. It uses one of the other ETLs that share a lookup to create a new entity. The default selection is False.

   Scheduling options

   Property	Description
   Hour mask	Specify a value to run the task only during particular hours within a day. For example, 0 – 23 or 1, 3, 5 – 12.
   Day of week mask	Select the days so that the task can be run only on the selected days of the week. To avoid setting this filter, do not select any option for this field.
   Day of month mask	Specify a value to run the task only on the selected days of a month. For example, 5, 9, 18, 27 – 31.
   Apply mask validation	Select False to temporarily turn off the mask validation without removing any values. The default selection is True.
   Execute after time	Specify a value in the hours:minutes format (for example, 05:00 or 16:00) to wait before the task is run. The task run begins only after the specified time is elapsed.
   Enqueueable	Specify whether you want to ignore the next run command or run it after the current task. Select one of the following options: False: Ignores the next run command when a particular task is already running. This is the default selection. True: Starts the next run command immediately after the current running task is completed.

   There is an addition property, extract.dynatrace.virtualNode, which enables virtual machines to be identified and labeled as such. They will be using the virtual node namespace as well.

   There is an addition property, extract.dynatrace.virtualNode, which enables virtual machines to be identified and labeled as such. They will be using the virtual node namespace as well.

    

3. Click Save.
   The ETL tasks page shows the details of the newly configured Dynatrace ETL.

After you configure the ETL, you can run it to collect data. You can run the ETL in the following modes:

A. Simulation mode: Only validates connection to the data source, does not collect data. Use this mode when you want to run the ETL for the first time or after you make any changes to the ETL configuration.

B. Production mode: Collects data from the data source.

A. Running the ETL in the simulation mode

To run the ETL in the simulation mode:

1. In the console, navigate to Administration > ETL & System Tasks, and select ETL tasks.
2. On the ETL tasks page, click the ETL.
   
   
3. In the Run configurations table, click Edit  to modify the ETL configuration settings.
4. On the Run configuration tab, ensure that the Execute in simulation mode option is set to Yes, and click Save.
5. Click Run active configuration. A confirmation message about the ETL run job submission is displayed.
6. On the ETL tasks page, check the ETL run status in the Last exit column.
   OK Indicates that the ETL ran without any error. You are ready to run the ETL in the production mode.
7.  If the ETL run status is Warning, Error, or Failed:
   1. On the ETL tasks page, click  in the last column of the ETL name row.
   2. Check the log and reconfigure the ETL if required.
   3. Run the ETL again.
   4. Repeat these steps until the ETL run status changes to OK.

B. Running the ETL in the production mode

You can run the ETL manually when required or schedule it to run at a specified time.

Running the ETL manually

1. On the ETL tasks page, click the ETL. The ETL details are displayed.
2. In the Run configurations table, click Edit  to modify the ETL configuration settings. The Edit run configuration page is displayed.
3. On the Run configuration tab, select No for the Execute in simulation mode option, and click Save.
4. To run the ETL immediately, click Run active configuration. A confirmation message about the ETL run job submission is displayed.
   When the ETL is run, it collects data from the source and transfers it to the database.

Scheduling the ETL run

By default, the ETL is scheduled to run daily. You can customize this schedule by changing the frequency and period of running the ETL.

To configure the ETL run schedule:

1. On the ETL tasks page, click the ETL, and click Edit.
   
   
2. On the Edit task page, do the following, and click Save:
   • Specify a unique name and description for the ETL task.
   • In the Maximum execution time before warning field, specify the duration for which the ETL must run before generating warnings or alerts, if any.
   • Select a predefined or custom frequency for starting the ETL run. The default selection is Predefined.
   • Select the task group and the scheduler to which you want to assign the ETL task.
3. Click Schedule. A message confirming the scheduling job submission is displayed.
   When the ETL runs as scheduled, it collects data from the source and transfers it to the database.

Verify that the ETL ran successfully and check whether the Dynatrace data is refreshed in the Workspace.

To verify whether the ETL ran successfully:

1. In the console, click Administration > ETL and System Tasks > ETL tasks.
2. In the Last exec time column corresponding to the ETL name, verify that the current date and time are displayed.

To verify that the Dynatrace data is refreshed:

1. In the console, click Workspace.
2. Expand (Domain name) > Systems > Dynatrace > Instances.
3. In the left pane, verify that the hierarchy displays the new and updated Dynatrace instances.
4. Click a Dynatrace entity, and click the Metrics tab in the right pane.
5. Check if the Last Activity column in the Configuration metrics and Performance metrics tables displays the current date.