ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (15.4.0) 15.3.0 15.2.0 15.1.0 14.5.x 13.9.x 13.8.x 13.7.x 13.6.x 13.5.0 13.4.x 13.3.x 13.2.x
User Community Service Desk Downloads
If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

Import Monitoring Project Configuration

It is possible to copy the configuration of one monitoring project and apply it to another, for example, to test new rules on a catalog item in a monitoring project without risking unnecessary changes in a production project. To see this in action, see Monitoring project lifecycles.

Configuration import includes:

  • All checks (structure checks, anomaly detection, DQ checks)

  • Invalid samples

  • Reports structure

  • DQ filters

To import a monitoring project:

  1. Select the project you want to import the configuration into. Using the three dots menu, select Import configuration.

    Import configuration

    1. On the Import monitoring project configuration screen, from the list provided, select the monitoring project from which the configuration should be used.

      Select source

  2. After selecting a project, some tables are preselected based on the Purpose assigned to catalog items.

  3. Check if the preselected catalog items are correct. If something is not correct, it is possible to delete it from the list or change it to another catalog item. Click on the cross icon to delete the catalog item from the list, or use the dropdown arrow to expand the list of all catalog items to choose from.

    When selecting a different catalog item, a warning may appear, due to the differences in structure of the expected catalog item and the one selected.

    Error

    It is not possible to copy the configuration unless the structure matches.

  4. When you are ready, select Start import at the bottom of the page. The configuration is copied to the new monitoring project immediately.

Set a Purpose

Setting the purpose for catalog items is optional, but it helps to preselect the catalog items for a monitoring project without assigning items to the monitoring project manually. To link the project with the catalog items, the same purpose needs to be set for both, project and items.

  • To set the purpose of the project, navigate to the Overview tab, click Add purpose, and select from the preconfigured list.

  • To set the purpose of catalog items, navigate to the Overview tab of the item, click Add purpose on the Purpose widget and select from the preconfigured. For more information, see Getting Started with ONE Data Catalog.

Monitoring project lifecycles

You can make use a combination of Purpose tags and of the import monitoring project configuration feature to simulate a multi-environment process (Configure > Test > Send for approval > Make public, and repeat) within one physical environment.

In summary:

  1. Create a project, use tables from the non-production data source, assign rules, and test.

  2. Create a second project and use the new Import configuration functionality, and import the configuration from the first project.

  3. Map tables to their non-production instances:

    • If catalog items have not been assigned a purpose tag, and this is the first import of the configuration, you need to map items manually.

    • If the configuration has been previously imported, mapping is automatic (this can be overridden by the user).

    • If catalog items have been assigned a purpose corresponding to that of the project, these items are selected.

Two physical environments can be created, but the intended use for the non-production environment should be only:

  • Testing new sources.

  • Testing new integration plans (for example, you have a workflow that reads or writes to API).

  • Testing model changes.

  • Testing service re-configurations (for example, you can change the settings in configuration files and check whether the platform remains stable).

These instances are not intended for:

  • Developing data quality monitoring projects and then migrating between them (that is, developing monitoring on DEV and then physically migrating to PROD). This would entail either manually propagating changes to the PROD environment, or creating migration scripts using built-in APIs, or custom APIs (usually implemented by plans and API steps).

The preferred method on multi-environments is one production environment for all metadata, and one non-production environment for model changes, API work, and testing. This differs to other products, for example, RDM and MDM, for which one production and two non-production environments are recommended.

Copying the configuration of a project means you can create, for example, a DEV and PROD instance of the same project, to test projects on non-production data and later exchange for production data.

This allows you to test rules and configurations, particularly how changes in rules affect monitoring projects, without affecting the production dashboard. It also means it is not necessary to configure the same project multiple times, which is highly valuable given that organizations can have large numbers of catalog items in a project with multiples rules for each table.

Create rules and connect them to your production and non-production data sets. Link the matching catalog items from each data set, and create two separate projects, for example, one for DEV and one for PROD. You can distinguish between these using the Purpose label.

It is only be necessary to configure one project, and you can then easily copy the configuration to the second project. In the guide that follows, we use the DEV and PROD example to illustrate this functionality.

Tutorial

  1. Add both a DEV and a PROD purpose in List of Values. For more details, see Lists of Values.

    1. In Global Settings > List of Values, select Add Data instance.

      List of values

    2. Provide a name (that is, DEV or PROD).

    3. Select Save

  2. Select an existing project to be used as the DEV instance, or configure one, for example, My project - dev.

    Project

  3. In General information, add a purpose for the monitoring project: DEV.

    Add purpose

  4. Create a monitoring project for the production environment, for example, My project - prod. You do not need to configure this project.

  5. In General information, add a purpose for the monitoring project: PROD.

  6. Copy the monitoring project configuration for My project - dev to My project - prod, that is, from the development environment to the production environment according to the instructions found earlier in this article.

Was this page useful?