Service Graph Connector for Microsoft Azure - Resource Inclusion Handling
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2024 09:00 AM
Hi,
Does anyone know of a method to selectively define generic cloud resource CI creation from SGC Azure?
For example if you want to prevent a specific generic cloud resource and allow other generic resources using SGC Azure.
I have two ideas that I’m noodling on: restrict the access to the resource object or disable the data import, both approaches are unappealing.
Does a method exists to define the generic resource types for SGC Azure perhaps like the Cloud Inventory Resource Inclusion approach used in patterned discovery?
Note from the SGC concept page:
Note: The connector utilizes the Service Graph Resource Inclusion Whitelist [sn_cmdb_int_util_service_graph_resource_inclusion_whitelist] table to differentiate between generic and other supported resource types.
The connector first populates all supported resources in the Service Graph Resource Inclusion Whitelist [sn_cmdb_int_util_service_graph_resource_inclusion_whitelist] table. These resources, categorized under their respective supported resource types, have specific data sources designated for ingestion within the connector. When the SG-Azure Generic Resources data source is executed and retrieves unsupported resource types, they are added to the Service Graph Resource Inclusion Whitelist [sn_cmdb_int_util_service_graph_resource_inclusion_whitelist] table and categorized as generic.
Service Graph Connector for Microsoft Azure (1.9.1) (servicenow.com)
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I have a similar requirements wherein
microsoft.alertsmanagement/actionrules
microsoft.alertsmanagement/smartdetectoralertrules
microsoft.app/jobs
microsoft.app/managedenvironments/certificates
microsoft.automation/automationaccounts/runbooks
microsoft.bing/accounts
microsoft.cognitiveservices/accounts/projects
microsoft.communication/communicationservices
microsoft.communication/emailservices/domains
microsoft.compute/galleries/images
microsoft.compute/galleries/images/versions
microsoft.compute/locations/usages
microsoft.compute/sshpublickeys
microsoft.compute/virtualmachines/extensions
microsoft.containerregistry/registries/replications
microsoft.containerregistry/registries/tasks
microsoft.insights/actiongroups
microsoft.insights/activitylogalerts
microsoft.insights/autoscalesettings
Microsoft.Insights/dataCollectionRules
microsoft.insights/metricalerts
microsoft.insights/privatelinkscopes
microsoft.insights/scheduledqueryrules
microsoft.insights/webtests
Microsoft.Network/dnsResolvers/inboundEndpoints
Microsoft.Network/dnsResolvers/outboundEndpoints
microsoft.network/networkintentpolicies
microsoft.network/networkmanagers
microsoft.network/networkmanagers/ipampools
microsoft.network/networkwatchers
microsoft.network/privatednszones/virtualnetworklinks
microsoft.network/serviceendpointpolicies
microsoft.portal/dashboards
microsoft.resources/deploymentscripts
microsoft.security/automations
microsoft.web/certificates
microsoft.web/connections
RESOURCE TYPES to be excluded to flood CMDB generic table. Asked SN for the resolution, the response I got was copy pasted from AI. Anybody has a solution which is more of configuration in nature.