o11y IM Importing custom Azure Monitor metrics

Available Languages

Updated:September 29, 2026

Document ID:SPLK045562

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Observability Cloud

Description

For AWS users are allowed to add custom namespaces to the integration via the UI. The Azure integration does not offer this option at this moment. However, it is possible to add monitoring of custom name spaces to the Azure integration by editing the integration object via the API.

Resolution

Please follow these steps:

====================

1. export the integration object via the API

- first use https://dev.splunk.com/observability/reference/api/integrations/latest/#endpoint-retrieve-integrations-query to get the integration id

- then https://dev.splunk.com/observability/reference/api/integrations/latest/#endpoint-retrieve-single-integration to get a clean json output of the integration object

2. make the changes in the json output

- add
"customNamespacesPerService": {"<context sensitive service name>" : ["customNamespace", "customNamespace2"]}

as the last line

- remove the lines containing appId and secretKey

- the service name you use is the one you used for your custom metric and must be supported, and then of course the custom namespace name for it. The supported Services are found in our integration documentation here:
https://help.splunk.com/en/splunk-observability-cloud/manage-data/connect-to-your-cloud-service-provider/connect-to-azure/supported-azure-services#d584ec9d9d5ee476ebd4f84c278ae41be--en__supported-azure-services

3. PUT the updated json output back to the system

- this is done via the API endpoint
https://dev.splunk.com/observability/reference/api/integrations/latest/#endpoint-update-single-integration

- this says update but what happens is that you exchange the current content with your adjusted content.

- the lines appId and secretKey are the only ones not being updated this way and always stay the same. In the json output you created earlier, you will see that these are blanked out. This is for security reasons.

https://help.splunk.com/en/splunk-observability-cloud/manage-data/connect-to-your-cloud-service-provider/connect-to-azure/supported-azure-services#d584ec9d9d5ee476ebd4f84c278ae41be--en__supported-azure-services

https://dev.splunk.com/observability/reference/api/integrations/latest/#endpoint-update-single-integration