Go to Storage Insights

Click the name of the dataset configuration that generated the datasetyou want to unlink.

In theBigQuery linked dataset section, clickUnlink dataset.

To unlink the dataset, run thegcloud storage insights dataset-configs delete-linkcommand:

gcloud storage insights dataset-configs delete-linkDATASET_CONFIG_ID --location=LOCATION

Replace:

• DATASET_CONFIG_ID with the name of thedataset configuration that generated the dataset you want to unlink.

• LOCATION with thelocation of yourdataset and dataset configuration. For example,us-central1.

You can also specify a full dataset configuration path. For example:

gcloud storage insights dataset-configs delete-link projects/DESTINATION_PROJECT_ID/locations/LOCATION/datasetConfigs/DATASET_CONFIG_ID

Replace:

• DESTINATION_PROJECT_ID with the ID of theproject that contains the dataset configuration. For more informationabout project IDs, seeCreating and managing projects.

• DATASET_CONFIG_ID with the name of thedataset configuration that generated the dataset you want to unlink.

• LOCATION with thelocationof your dataset and dataset configuration. For example,us-central1.

Have gcloud CLIinstalled and initialized, which lets you generate an access token for theAuthorization header.

Create a JSON file that contains the following information:

{"name":"DATASET_NAME"}

UsecURL to call theJSON API with anunlinkDataset DatasetConfig request:

curl --request POST --data-binary @JSON_FILE_NAME \"https://storageinsights.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/datasetConfigs/DATASET_CONFIG_ID:unlinkDataset?" \  --header "Authorization: Bearer $(gcloud auth print-access-token --impersonate-service-account=SERVICE_ACCOUNT)" \  --header "Accept: application/json" \  --header "Content-Type: application/json"

Replace:

• JSON_FILE_NAME with the path to theJSON file you created in the previous step.

• PROJECT_ID with theID of the project that the dataset configuration belongs to.

• LOCATION with thelocation of thedataset and dataset configuration. For example,us-central1.

• DATASET_CONFIG_ID with the nameof the dataset configuration that generated the dataset you wantto unlink.

• SERVICE_ACCOUNT with the service account. For example,test-service-account@test-project.iam.gserviceaccount.com.

Go to Storage Insights

Click the name of the dataset configuration you want to view.

The dataset configuration details are displayed.

To describe a dataset configuration, run thegcloud storage insights dataset-configs describecommand:

gcloud storage insights dataset-configs describeDATASET_CONFIG_ID \  --location=LOCATION

Replace:

• DATASET_CONFIG_ID with the nameof the dataset configuration.

• LOCATION with the location of the dataset anddataset configuration.

You can also specify a full dataset configuration path. For example:

gcloud storage insights dataset-configs describe projects/DESTINATION_PROJECT_ID/locations/LOCATION/datasetConfigs/DATASET_CONFIG_ID

Replace:

• DESTINATION_PROJECT_ID with the ID of theproject that contains the dataset configuration. For more informationabout project IDs, seeCreating and managing projects.

• DATASET_CONFIG_ID with the name of thedataset configuration that generated the dataset you want to view.

• LOCATION with thelocationof your dataset and dataset configuration. For example,us-central1.

Have gcloud CLIinstalled and initialized, which lets you generate an access token for theAuthorization header.

UsecURL to call theJSON API with anGet DatasetConfig request:

curl -X GET \"https://storageinsights.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/datasetConfigs/DATASET_CONFIG_ID" \  --header "Authorization: Bearer $(gcloud auth print-access-token --impersonate-service-account=SERVICE_ACCOUNT)" \  --header "Accept: application/json" \  --header "Content-Type: application/json"

Replace:

• PROJECT_ID with theID of the project that the dataset configuration belongs to.

• LOCATION with thelocation of thedataset and dataset configuration. For example,us-central1.

• DATASET_CONFIG_ID with the nameof the dataset configuration.

• SERVICE_ACCOUNT with the service account. For example,test-service-account@test-project..

Go to Storage Insights

The list of dataset configurations is displayed.

To list dataset configurations in a project, run thegcloud storage insights dataset-configs listcommand:

gcloud storage insights dataset-configs list --location=LOCATION

Replace:

• LOCATION with thelocation of thedataset and dataset configuration. For example,us-central1.

You can use the following optional flags to specify the behavior of thelisting call:

• Use--page-size to specify the maximum number of resultsto return per page.

• Use--filter=FILTER to filter results. Formore information on how to use the--filter flag, rungcloud topic filters and refer to the documentation.

• Use--sort-by=SORT_BY_VALUE to specifya comma-separated list of resource field key names to sort by.For example,--sort-by=DATASET_CONFIG_ID.

Have gcloud CLIinstalled and initialized, which lets you generate an access token for theAuthorization header.

UsecURL to call theJSON API with aGet DatasetConfig request:

curl -X GET \"https://storageinsights.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/datasetConfigs" \  --header "Authorization: Bearer $(gcloud auth print-access-token --impersonate-service-account=SERVICE_ACCOUNT)" \  --header "Accept: application/json" \  --header "Content-Type: application/json"

Replace:

• PROJECT_ID with theID of the project that the dataset configuration belongs to.

• LOCATION with thelocation of thedataset and dataset configuration. For example,us-central1.

• SERVICE_ACCOUNT with the service account. For example,test-service-account@test-project.iam.gserviceaccount.com.

Go to Storage Insights

Click the name of the dataset configuration you want to update.

In theDataset configuration tab, clickEditeditto update the fields.

To update a dataset configuration, run thegcloud storage insights dataset-configs updatecommand:

gcloud storage insights dataset-configs updateDATASET_CONFIG_ID \  --location=LOCATION

Replace:

• DATASET_CONFIG_ID with the nameof the dataset configuration.

• LOCATION with the location of the datasetand dataset configuration.

Use the following flags to update properties of the dataset configuration:

• Use--skip-verification to skip checks and failures fromthe verification process, which includes checks for requiredIAM permissions. If used, some or all buckets mightbe excluded from the dataset.

• Use--retention-period-days=DAYS to specify themoving number of days of data to capture in the dataset snapshot. Forexample,90.

• Use--activity-data-retention-period-days=ACTIVITY_RETENTION_PERIOD_DAYSto specify the retention period for theactivity data in thedataset. By default, activity data is included in the dataset, andinherits the retentionperiod of the dataset. To override the dataset retention period,specify the number of days to retain activity data for. To excludeactivity data, set theACTIVITY_RETENTION_PERIOD_DAYS to0.

• Use--description=DESCRIPTION to writea description for the dataset configuration.

• Use--organization=ORGANIZATION_ID to specifythe organization ID of the source project. If unspecified, defaults tothe source project's organization ID.

Have gcloud CLIinstalled and initialized, which lets you generate an access token for theAuthorization header.

Create a JSON file that contains the following optional information:

{"organization_number":"ORGANIZATION_ID","source_projects":{";project_numbers":"PROJECT_NUMBERS"},"retention_period_days":"RETENTION_PERIOD","activityDataRetentionPeriodDays":"ACTIVITY_DATA_RETENTION_PERIOD_DAYS"}

• ORGANIZATION_ID with the resource ID oftheorganization to which the source projects belong to. Ifunspecified, defaults to the source project's organization ID.

• PROJECT_NUMBERS with theproject numbers to include in the dataset. You canspecify one or more projects in a list format.

• RETENTION_PERIOD with the movingnumber of days of data to capture in the dataset snapshot. Forexample,90.

• ACTIVITY_DATA_RETENTION_PERIOD_DAYS withthe number of days ofactivity data to capture in thedataset snapshot. By default, activity data is included in thedataset, and inherits the retentionperiod of the dataset. To override the dataset retention period,specify the number of days to retain activity data for. To excludeactivity data, set theACTIVITY_RETENTION_PERIOD_DAYS to0.

To update the dataset configuration, usecURL to call theJSON API with aPatch DatasetConfig request:

curl -X PATCH --data-binary @JSON_FILE_NAME \"https://storageinsights.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/datasetConfigs/DATASET_CONFIG_ID?updateMask=UPDATE_MASK" \  --header "Authorization: Bearer $(gcloud auth print-access-token --impersonate-service-account=SERVICE_ACCOUNT)" \  --header "Accept: application/json" \  --header "Content-Type: application/json"

Replace:

• JSON_FILE_NAME with the path to the JSON file you created in the previous step.

• PROJECT_ID with theID of the project that the dataset configuration belongs to.

• LOCATION with thelocation of thedataset and dataset configuration. For example,us-central1.

• DATASET_CONFIG_ID with the name ofthe dataset configuration you want to update.

• UPDATE_MASK is the comma-separated list of field names thatthis request updates. The fields use thefieldMask format and are part of theDatasetConfig resource.

• SERVICE_ACCOUNT with the service account. For example,test-service-account@test-project.iam.gserviceaccount.com.

Go to Storage Insights

Click the name of the dataset configuration you want to delete.

ClickDeletedelete.

To delete a dataset configuration, run thegcloud storage insights dataset-configs deletecommand:

gcloud storage insights dataset-configs deleteDATASET_CONFIG_ID \  --location=LOCATION

Replace:

• DATASET_CONFIG_ID with the nameof the dataset configuration you want to delete.

• LOCATION with thelocation of thedataset and dataset configuration. For example,us-central1.

Use the following flags to delete a dataset configuration:

• Use--auto-delete-link to unlink the dataset that wasgenerated from the dataset configuration you want to delete. You mustunlink a dataset before you can delete the dataset configuration thatgenerated the dataset.

You can also specify a full dataset configuration path. For example:

gcloud storage insights dataset-configs delete projects/DESTINATION_PROJECT_ID/locations/LOCATION/datasetConfigs/DATASET_CONFIG_ID

Have gcloud CLIinstalled and initialized, which lets you generate an access token for theAuthorization header.

UsecURL to call theJSON API with anDelete DatasetConfig request:

curl -X DELETE \  "https://storageinsights.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/datasetConfigs/DATASET_CONFIG_ID" \  --header "Authorization: Bearer $(gcloud auth print-access-token --impersonate-service-account=SERVICE_ACCOUNT)" \    --header "Accept: application/json" \    --header "Content-Type: application/json"

Replace:

• PROJECT_ID with theID of the project that the dataset configuration belongs to.

• LOCATION with thelocation of thedataset and dataset configuration. For example,us-central1.

• DATASET_CONFIG_ID with the name ofthe dataset configuration you want to delete.

• SERVICE_ACCOUNT with the service account. For example,test-service-account@test-project.iam.gserviceaccount.com.