InlineSegmentationSessionSettings1
InlineSegmentationSessionSettings1
JSON Example
{
"_create_user": "system",
"_create_time": 1781138986404,
"_last_modified_user": "admin",
"_last_modified_time": 1781139555120,
"_revision": 1,
"id": "f4a7eb15-43c4-44cb-ac5c-8a5d5c15235b",
"display_name": "settings_f4a7eb15-43c4-44cb-ac5c-8a5d5c15235b",
"site_ids": [],
"csv_mappings": {
"asset_identifiers": [
"asset id",
"asset name",
"asset ip"
],
"columns": [
"asset type",
"asset name",
"asset ip",
"asset id",
"infrastructure service",
"region",
"zone",
"environment",
"application",
"application tier"
],
"asset_type": "asset type",
"hierarchy_scopes": {
"region_scope": "region",
"zone_scope": "zone",
"environment_scope": "environment",
"application_scope": "application",
"application_tier_scope": "application tier"
},
"infrastructure_service": "infrastructure service"
},
"allow_existing_group_rename": true
}
csv_mappings
Optional
Defines how CSV columns map to segmentation concepts. This configuration tells the analysis engine which columns contain asset identifiers, types, and hierarchy information. When provided, certain fields become required to ensure valid mapping.
Notes:
asset_identifiers(1-3 columns) must be set before triggeringPARSE_FILE; the analysis engine uses these columns to match CSV rows to NSX entities (VMs, segments, etc.).columnsis a read-only field auto-detected from the CSV header row; it cannot be set by clients.- If
asset_typeis omitted, the system will attempt to auto-detect asset types from the column values.
boolean
allow_existing_group_rename
Optional
Controls whether existing groups should be renamed during promotion. If true, groups will be renamed to match the segmentation naming convention. If false, existing group names will be preserved.