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 Spike 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 |
|---|---|---|---|
| Integrations | Integration | spike:integrations |
Every 12 hours (0 */12 * * *) |
For schema attribute definitions, refer to Integration 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:
- Go to Admin > Connections > Sources, and open your source.
- Go to Dataset Management > Datasets.
- Select the dataset you want to configure.
-
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.
- 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.
- 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 Spike source lists each object type that is aggregated. Select a resource to review its schema on the Schema tab.
| Resource name | Resource type | Resource ID |
|---|---|---|
| Integration | std:application |
spike:integration |
Owner Correlation
On the Owner Correlation tab of the Integration resource, map the integration to the identity that owns it. For more information, refer to Owner Correlation.
Integration Attributes
The Integration resource is in the Integrations dataset.
| Field | Value |
|---|---|
| Resource ID | spike:integration |
| Resource type | std:application |
| Identity attribute | ID |
| Display attribute | Name |
The following table lists the schema attributes for the Integration resource:
| Attribute Name | Description |
|---|---|
| ID | Object ID of the integration. |
| Name | Name set for the integration. |
| Slug | Integration type, such as apex-ping or webhook. |
| Token | Webhook token the external system uses to open incidents. Spike addresses the integration by this value. Treat it as a sensitive credential. |
| Auth Enabled | Whether an additional authentication check is enabled on the integration. |
| Disabled | Whether the integration is disabled. |
| Archive | Whether the integration is archived. |
| Service | ID of the service incidents from this integration are attributed to. |
| Escalation | ID of the escalation policy that pages responders for this integration. |
| Teams | IDs of the teams this integration belongs to. |
| Organization | ID of the organization this integration belongs to. |
| Created By | ID of the user who created the integration. This is the same identifier aggregated as the account ID. |
| Created At | ISO 8601 date-time when the integration was created. |
| Updated At | ISO 8601 date-time when the integration was last updated. |
| Last Incident At | ISO 8601 date-time of the latest incident opened through this integration. |
| Repeat Escalation | Whether escalation repeats when an incident is not acknowledged. |
| Disable Incident Suppression | Whether duplicate-incident suppression is disabled. |
| Email Hooks | Whether the integration accepts incidents by email. |
| Custom Parser Enabled | Whether a custom payload parser is enabled. |
| Timer Resolve Enabled | Whether incidents from this integration auto-resolve on a timer. |
| Total Incidents | Total incidents opened through this integration. |
| Open Incidents | Incidents from this integration that are still open. |
| Default | Whether this is a default integration. |
| Copies Created | Number of copies created from this integration. |