Monitoring Microsoft Purview
Microsoft Purview provides a unified data governance solution to help manage cloud data. Instana uses the Microsoft Purview sensor to monitor Microsoft Purview service in Azure. Instana comprehensively monitors the Microsoft Purview service by providing end-to-end visibility into your environment.
For more information about other supported Azure services, see Monitoring and Instrumenting Microsoft® Azure with Azure agent.
Configuring the Microsoft Purview sensor
To configure the Microsoft Purview sensor, complete the following steps:
-
Enable the Azure service subscription in Instana. Update the
<agentinstall_dir>/etc/instana/configuration.yamlagent configuration file as shown in the following example:com.instana.plugin.azure: enabled: true subscription: "[Your-Subscription-Id]" tenant: "[Your-Tenant-Id]" principals: - id: "[Your-Service-Principal-Account-Id]" secret: "[Your-Service-Principal-Secret]"For more information about installing the Azure agent, see Installing the Instana agent.
-
Enable the Microsoft Purview sensor in the agent configuration file. You can also configure tags and resource groups as described in the Filtering services by defining tags and resource groups section. To enable the Microsoft Purview sensor, update the
<agentinstall_dir>/etc/instana/configuration.yamlagent configuration file as shown in the following example:com.instana.plugin.azure.purview: enabled: true
Filtering services by defining tags and resource groups
To define multiple tags and resource groups, separate them with
commas. Define the tags as a key-value pair that is separated by a
colon (:). You can define multiple tags and resource
groups in the configuration.yaml file. Use commas to
separate multiple tags or resource groups. If you define a tag or
resource group in both lists (include and exclude), the excluded
list has higher priority. If you want to include all services
without filtering, avoid defining any configuration.
-
To set tags for the include list, update the
configuration.yamlfile as shown in the following example:com.instana.plugin.azure.purview: include_tags: # Comma separated list of tags in key:value format (e.g. env:prod,env:staging) -
To set tags for the exclude list, update the
configuration.yamlfile as shown in the following example:com.instana.plugin.azure.purview: exclude_tags: # Comma separated list of tags in key:value format (e.g. env:dev,env:test) -
To set resource groups for the include list, update the
configuration.yamlfile as shown in the following example:com.instana.plugin.azure.purview: include_resource_groups: # Comma separated list of resource groups (e.g. rg_prod,rg_staging) -
To set resource groups for the exclude list, update the
configuration.yamlfile as shown in the following example:com.instana.plugin.azure.purview: exclude_resource_groups: # Comma separated list of resource groups (e.g. rg_dev,rg_test)
Disabling the Microsoft Purview sensor
To disable monitoring the Microsoft Purview services, update the
<agentinstall_dir>/etc/instana/configuration.yaml
agent configuration file as shown in the following example:
com.instana.plugin.azure.purview:
enabled: false
Viewing metrics
To view the metrics, complete the following steps:
- From the navigation menu in the Instana UI, select Infrastructure.
- Click a specific monitored host.
You can see a host dashboard with all the collected metrics and monitored processes.
The following types of metrics are pulled:
- Scan metrics are pulled every 1 minute.
- Data map metrics are pulled every 1 hour.
Configuration data
| Purview details | Description |
|---|---|
| Name | Name of the purview account |
| Resource Group | Resource group of the purview account |
| Location | Location of the purview account |
| Type | Type of the resource |
| CreatedAt | Creation time of the purview account |
| SubscriptionID | Subscription ID of the purview account |
Performance metrics
| Metric | Name | Unit | Aggregation | Description |
|---|---|---|---|---|
| Scan | ||||
| Scan Cancelled | ScanCancelled | Count | Count | The number of scans that are cancelled. |
| Scan Completed | ScanCompleted | Count | Count | The number of scans that are completed successfully. |
| Scan Failed | ScanFailed | Count | Count | The number of scans failed. |
| Scan time taken | ScanTimeTaken | Seconds | Average | The total scan time in seconds. |
| Data Map | ||||
| Data Map Capacity Units | DataMapCapacityUnits | Count | Count | Capacity of Data Map in Units. |
| Data Map Storage Size | DataMapStorageSize | Bytes | Average | Storage size of the Data Map. |