Azure Troubleshooting

Azure Troubleshooting

このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。

Find your tenant name

  1. Navigate to portal.azure.com.
  2. In the left sidebar, select Azure Active Directory.
  3. Under Properties, your tenant name is the Directory ID value.

Your tenant name is also available from the URL when using the classic portal. It is the text in between (not including) the @ and # symbol:

Unable to login

If you experience an error logging in while trying to install the Azure integration, contact Datadog support. When possible, attach a screenshot.

Missing metrics

Ensure you completed the installation process, which includes giving read permissions to the Azure application for the subscriptions you want to monitor.

For ARM deployed virtual machines, you must also turn on Diagnostics and select the VM metrics you would like to collect. See Enable Diagnostics below for instructions.

For other missing metrics, contact Datadog support.

Enable diagnostics

Turning on Diagnostics allows ARM deployed VMs to collect logging information which includes metrics for CPU, Network, etc. Follow these instructions:

  1. Navigate to the Azure portal and locate your VM.

  2. Click on Diagnostics settings under the Monitoring section.

  3. Pick a storage account and click Enable guest-level monitoring.

  4. By default, basic metrics and logs are enabled. Adjust based on your preferences.

  5. Click Save to save any changes.

Automated log collection

Naming conflicts

If you have Azure resources with the same resource name as one of the default parameters, it can lead to naming conflicts. Azure does not allow resources to share resource names within an individual subscription. Datadog recommends renaming the default parameter with a unique name that does not already exist within your environment.

For example, use the -EventhubName flag to change the default name of the eventhub resource, if you already possess an eventhub named ‘datadog-eventhub’.

Example

./resource_deploy.ps1 -ApiKey <your_api_key> -SubscriptionId <your_subscription_id> -EventhubName <new-name>

Note: Navigate to the Optional Parameters section to find the list of configurable parameters.

Note: If you are re-running the script due to this failure, it is also advised that you remove the entire resource group to create a fresh execution.

Unregistered resource provider

If your script execution is failing due to the error The subscription is not registered to use namespace ‘Microsoft.EventHub’:

Azure has resource providers for each of its services, for example: Microsoft.EventHub for the Azure EventHub. If your Azure subscription is not registered to a required resource provider the script fails. You can fix this issue by registering with the resource provider. Run this command in CloudShell.

Example

az provider register --namespace Microsoft.EventHub

Exceeding log quota

Did you install the script successfully, but you are still not seeing activity/platform logs within the Logs Explorer?

Ensure that you have not exceeded your daily quota for log retention.

Note: It is advised that you take at least five minutes after the execution of the script to start looking for logs in the Logs Explorer.

Further Reading

お役に立つドキュメント、リンクや記事: