# Dataset Management Dataset Management lets you review the object types a source collects and control how the source aggregates those objects into SailPoint. Use Dataset Management to view and manage resource attributes, datasets and their resources, enable dataset aggregation schedules, perform manual aggregation, and view aggregation history. > [!NOTE] > > Datasets are also available in SailPoint Agentic Fabric. Contact your Customer Success team and refer to [SailPoint Agentic Fabric]() for more information. For more information, refer to [Managing Datasets and Resources]() for datasets, resources, owner correlation, and aggregation. ## Datasets A *dataset* is a named group of one or more related resources that the source aggregates together. When aggregation runs for a dataset, the source collects all resources in that dataset from the managed system in one aggregation job. Activate or deactivate aggregation at the dataset level, not for individual resources. > [!NOTE] > > Each resource belongs to exactly one dataset for that source. The source defines which resources belong to each dataset. You can enable aggregation and review associated resources, but you cannot create or delete datasets or move resources between them. ### Dataset Aggregation Configure aggregation on the **Dataset Aggregations** tab for each dataset. Configure each dataset separately. During aggregation, your owner correlation rules are automatically applied to link machine identities to their human owners. For more information, refer to [Configuring Dataset Aggregations](). ## Resources A resource defines an object type from the managed system. It specifies the kind of object, the attributes the source collects, and how the source identifies and displays each object. Resources form the building blocks of the data model. In the UI, each resource appears under **Dataset Management** \> **Resources** with its schema. A resource does not run aggregation by itself. The dataset that owns the resource collects it during aggregation. For more information, refer to [Managing Resources](). ### Owner Correlation Configure owner correlation on each resource to link aggregated objects to human owners. If you do not configure owner correlation, or if the mapping produces no match, an owner is not assigned. For more information, refer to [Configuring Owner Correlation](). ## Supported Datasets Go to **Dataset Management \> Datasets** on your BlazeMeter source to view the datasets the connector aggregates. Select a dataset to review its associated resources and configure aggregation. > [!NOTE] > > Configure aggregation for each dataset separately. For more information, refer to [Dataset Aggregation](). | Dataset name | Associated resources | Dataset ID | Aggregation schedule | | --- | --- | --- | --- | | **Test Schedule** | Test Schedule | `blazemeter:test-schedule` | Every 12 hours (`0 */12 * * *`) | For resource schema attributes, refer to [Supported Resources](<#supported-resources>) and [Test Schedule Attributes](<#test-schedule-attributes>). ### Dataset Aggregations Dataset aggregation collects resource objects from the managed system and loads them into SailPoint. Repeat the configuration for each dataset on the source. ### Configuring Dataset Aggregation To configure dataset aggregation for a dataset: 1. Go to **Admin \> Connections \> Sources**, and open your source. 2. Go to **Dataset Management \> Datasets**. 3. Select the dataset you want to configure. 4. Select the **Dataset Aggregations** tab. On the **Dataset Aggregations** tab, configure how resource objects from the selected dataset are aggregated into SailPoint. The tab contains **Scheduled Aggregations**, **Manual Aggregation**, and **Latest Aggregation**. #### Scheduled Aggregations Scheduled aggregations run on a schedule to keep the dataset synchronized with the managed system. 1. On the **Dataset Aggregations** tab, select **Enable Schedule** to turn on scheduled aggregations. When scheduled aggregations are enabled, SailPoint aggregates all resource objects in the dataset on the configured schedule. #### Manual Aggregation Manual aggregation runs once and collects all resource objects in the dataset. 1. On the **Dataset Aggregations** tab, select **Start Aggregation**. SailPoint starts the aggregation immediately. When the run completes, results appear in the **Latest Aggregation** section. #### Viewing Aggregation Results After an aggregation completes, review its status in the **Latest Aggregation** section on the **Dataset Aggregations** tab. The **Latest Aggregation** section shows: - **Start Time** - when the aggregation started - **Resource Objects Scanned** - the number of resource objects the aggregation processed - **Status** - whether the aggregation succeeded or failed Select **Details** to view additional information about the most recent run. To view prior runs, select **Aggregation History**. ## Supported Resources For more information, refer to [Managing Resources](). > [!NOTE] > > When you enable dataset aggregation for a selected dataset, all resources in that dataset are collected at once. Activate or deactivate aggregation at the dataset level, not for individual resources. Under **Dataset Management** \> **Resources**, the BlazeMeter source lists each object type that is aggregated. Select a resource to review its schema on the **Schema** tab. > [!NOTE] > > Test schedules are aggregated as application resources and are not included in user account aggregation. | Resource name | Resource type | Resource ID | Identity attribute | Display attribute | | --- | --- | --- | --- | --- | | **Test Schedule** | `std:application` | `blazemeter:test-schedule` | `id` | `cron` | For the complete resource schema, refer to [Test Schedule Attributes](<#test-schedule-attributes>). ### Owner Correlation On the **Owner Correlation** tab for the Test Schedule resource, map the schedule to the identity that owns it. Match the schedule `createdById` attribute to the user account `id`. Use the matched user's `email` to correlate to the SailPoint identity. Do not use `lastUpdatedById` for owner correlation. For more information, refer to [Owner Correlation](). ## Test Schedule Attributes Use the following schema attributes for the **Test Schedule** resource in the **Test Schedule** dataset. > [!NOTE] > > Use `createdById` for owner correlation. Match it to the user account `id`, then use that user's `email` to correlate to the SailPoint identity. Do not use `lastUpdatedById` for owner correlation. | Attribute Name | Description | | --- | --- | | id | Unique identifier of the test schedule. Resource ID. Required. | | cron | Cron expression defining when the scheduled test runs. Resource name and display attribute. Required. | | enabled | Whether the schedule is enabled and can trigger test runs. Required. | | type | Schedule execution type, such as testRun. Required. | | nextRun | Next scheduled execution time as a Unix epoch timestamp in seconds. | | isPrivateCloud | Whether the schedule belongs to a BlazeMeter Private Cloud deployment. | | created | Schedule creation time as a Unix epoch timestamp in seconds. | | updated | Last schedule update time as a Unix epoch timestamp in seconds. | | testId | Identifier of the test executed by this schedule. Present for a single test. | | testCollectionId | Identifier of the multi-test executed by this schedule. Present instead of testId for a multi-test. | | createdById | Identifier of the human user who created the schedule. Owner correlation attribute. Match it to the user id. | | lastUpdatedById | Identifier of the human user who last updated the schedule. Not the owner. | | firstFailureDate | Time of the schedule's first recorded execution failure as a Unix epoch timestamp in seconds. |