This feature isn’t available to all Palo Alto Networks Cortex XCOR users and
might not be visible in your app. For information about enabling this feature in your
environment, contact Cortex XCOR Support.
Supported telemetry types
The Microsoft Azure integration supports these telemetry types:Create the Azure principal
Configure Azure to let Cortex XCOR collect metrics:-
Create a dedicated Azure managed identity. Assign the built-in
Readerrole for every subscription you want to collect. As a best practice, use the identity only for Cortex XCOR to isolate its Azure API quota usage from other workloads. -
Retrieve the
credential_issuerandcredential_subjectfor your tenant. Cortex XCOR displays both values in two places:- In the Integrations Hub, select Azure. The Your federated credential values panel on the Overview tab lists them as Issuer and Subject.
- Click your profile icon from the menu bar and select My Account. The values are displayed next to Azure Federated Credential Issuer and Azure Federated Credential Subject.
-
Copy the
credential_issuerandcredential_subjectvalues exactly into a federated identity credential on the managed identity. -
When creating the Azure principal, grant it access to subscriptions using one of
the following options:
- Management group-based: Grant access at the Azure Management Group level. The integration collects subscriptions in each management group that the managed identity can access. Changes to management group membership change the subscriptions visible to the integration. You can grant the same managed identity access to multiple management groups.
- Subscription-based: Grant access to individual subscriptions. Update the role assignments when you add or remove subscriptions. The integration doesn’t collect subscriptions that the managed identity can’t access.
-
Record the
azure_tenant_idandidentity_client_idTerraform outputs shown in the following examples. Use these values to configure the integration in Cortex XCOR.
Terraform examples
The following examples show how you can integrate Azure using one of the previously mentioned methods:- Management group
- Individual subscription
The following Terraform code provides an example of how to create an Azure principal
and grant it access to the subscriptions within a management group.
Terraform example
Set up Cortex XCOR to receive Azure data
After configuring Azure to enable access to metrics, you must configure Cortex XCOR to receive and process those metrics. To access the Cortex XCOR API directly, see the Cortex XCOR API for Azure metrics.View Azure metrics integrations
To list or view Azure metrics integrations, use one of the following options:- Web
- Chronoctl
- API
In the Cortex XCOR Integrations Hub,
select Microsoft Azure, then select Configurations. Select a configuration to
view its details.
Create or update an Azure metrics integration
Create or update an Azure metrics integration using the Integrations Hub, Chronoctl, Terraform, or the Cortex XCOR API. The Integrations Hub requires the Editor or SysAdmin role. Chronoctl, Terraform, and the API require the SysAdmin role.- Web
- Chronoctl
- Terraform
- API
In the Cortex XCOR Integrations Hub,
select Microsoft Azure, then select Configurations. Add a configuration or
select an existing configuration to edit. Enter the managed identity’s tenant ID and
client ID, configure the metrics to collect, and save the configuration.
NAME: (string) The name of the Azure integration.SLUG: (string) The unique identifier of the Azure integration.TENANT_ID: (UUID) The ID of the Azure tenant that hosts the managed identity principal.CLIENT_ID: (UUID) The OAuth 2.0 client ID of the managed identity principal.RESOURCE_TYPE_NAME: (string) Name of an Azure resource type.METRIC_NAME: (string) Name of a metric for the resource type. Leave the metric list empty to retrieve all metrics.LOCATION: (string) Azure location to collect. Leave the locations list empty to retrieve all locations.SUBSCRIPTION_ID: (string) Azure subscription to collect. Leave the subscription list empty to retrieve all subscriptions.USAGE_METRICS_ENABLED: (Boolean) Enables collection of Azure usage metrics under this principal (Microsoft.Compute,Microsoft.Network,Microsoft.Storage).COUNT_METRICS_ENABLED: (Boolean) Enables Azure count metrics for the configured resources.PROPAGATE_TAGS: (Boolean) Specifies whether Azure resource, group, and subscription tags should be propagated as metric labels.
Delete an Azure integration
Delete an Azure integration using one of the following methods:- Web
- Chronoctl
- API
In the Cortex XCOR Integrations Hub,
select Microsoft Azure, then select Configurations. Open the configuration and
delete it. This action requires the Editor or SysAdmin role.
Validate metrics ingestion
After you save the integration, allow time for Azure to publish metrics and for Cortex XCOR to collect them. In Metrics Explorer, run:Metric information
Cortex XCOR ingests a wide range of Azure metrics. See the list of available Azure metrics.Metrics availability
By default, Cortex XCOR waits two minutes before collecting the newest Azure metric points and uses a minimum two-minute collection interval. A metric’s Azure time grain or a resource-specific collection setting can increase that interval. Some resources use collection delays of up to 10 minutes. Additional delay depends on when Azure publishes each metric. If a monitor evaluates before its Azure data arrives, use the PromQLoffset modifier
to add offsets to your monitors.
Points that arrive outside an aggregation rule’s late-data buffer can be omitted from
the aggregated metric even when the raw metric point is available.
Metric semantics
By default, metric names start withazure_. The configured metric-name prefix can
change this prefix. Metric names end in _avg, _min, _max, _count, or _total
to identify the Azure aggregation.
Cortex XCOR converts Azure’s Average, Minimum, and Maximum aggregations to
gauges. It converts Count and Total aggregations to delta counters: each point
represents the value during Azure’s aggregation interval, not a cumulative value.
Total points can be negative. To total Count or Total values across a query
window, use sum_over_time() instead of rate() or increase().
Metric labels
Standard Azure resource metrics include thesubscription_id, resource_group,
resource_type, resource_name, and location labels. Usage and metadata-derived
metrics can have different label sets. Azure metric dimensions are also converted to
labels.
To add tenant-level custom labels to Azure metrics, contact
Cortex XCOR Support. These labels are
configured for your deployment rather than on an individual Azure integration. If a
custom label has the same normalized name as an existing metric label, the custom
label value overwrites the existing value.
When Propagate tags is enabled, Azure subscription, resource-group, and resource
tags are normalized and added as labels. Resource tags take precedence over
resource-group tags, which take precedence over subscription tags. Propagated tags
also overwrite existing metric and custom labels with the same normalized name. For
example, a propagated Azure tag that normalizes to location overwrites the metric’s
existing location label.
Find Azure metrics in Metrics Explorer
Use Metrics Explorer to find and review the status of your ingested metrics.-
By default, Azure metrics start with the prefix
azure_. Search for the configured prefix to display Azure metrics in the platform. -
Search supports substrings. For example, if the original Azure metric name
contains a substring like
storageAccounts, searching for the substring returns the Azure metric, along with other metrics containing the substring.
Troubleshooting
The following table lists common problems and how to resolve them:Limitations
- The integration collects Azure Monitor platform metrics. It doesn’t collect Azure logs or traces.
- The integration can collect only subscriptions and resources visible to the managed identity.
- Propagated Azure tags can overwrite another label after label-name normalization.