Link to existing Datadog organization
Prerequisites
Before creating your first instance of Datadog - An Azure Native ISV Service, configure your environment. These steps must be completed before continuing with the next steps in this quickstart.
Find offer
Use the Azure portal to find Datadog - An Azure Native ISV Service.
Go to the Azure portal and sign in.
If you've visited the Marketplace in a recent session, select the icon from the available options. Otherwise, search for Marketplace.
In the Marketplace, search for Datadog - An Azure Native ISV Service.
In the plan overview screen, select Set up + subscribe.
Link to existing Datadog organization
The portal displays a selection asking whether you would like to create a Datadog organization or link Azure subscription to an existing Datadog organization.
If you're linking to an existing Datadog organization, select Create under the Link Azure subscription to an existing Datadog organization
You can link your new Datadog resource in Azure to an existing Datadog organization in US3.
The portal displays a form for creating the Datadog resource.
Provide the following values.
Property | Description |
---|---|
Subscription | Select the Azure subscription you want to use for creating the Datadog resource. You must have owner access. |
Resource group | Specify whether you want to create a new resource group or use an existing one. A resource group is a container that holds related resources for an Azure solution. |
Resource name | Specify a name for the Datadog resource. This name is the name of the new Datadog organization, when creating a new Datadog organization. |
Location | Select West US 2. Currently, West US 2 is the only supported region. |
Select Link to Datadog organization. The link opens a Datadog authentication window. Sign in to Datadog.
By default, Azure links your current Datadog organization to your Datadog resource. If you would like to link to a different organization, select the appropriate organization in the authentication window.
Select Next: Metrics and logs to configure metrics and logs.
If the subscription is already linked to an organization through a Datadog resource, an attempt to link the subscription to the same organization through a different Datadog resource would be blocked. It's blocked to avoid scenarios where duplicate logs and metrics get shipped to the same organization for the same subscription.
Configure metrics and logs
Use Azure resource tags to configure which metrics and logs are sent to Datadog. You can include or exclude metrics and logs for specific resources.
Tag rules for sending metrics are:
- By default, metrics are collected for all resources, except Virtual Machines, Virtual Machine Scale Sets, and App Service Plans.
- Virtual Machines, Virtual Machine Scale Sets, and App Service Plans with Include tags send metrics to Datadog.
- Virtual Machines, Virtual Machine Scale Sets, and App Service Plans with Exclude tags don't send metrics to Datadog.
- If there's a conflict between inclusion and exclusion rules, exclusion takes priority
Tag rules for sending logs are:
- By default, logs are collected for all resources.
- Azure resources with Include tags send logs to Datadog.
- Azure resources with Exclude tags don't send logs to Datadog.
- If there's a conflict between inclusion and exclusion rules, exclusion takes priority.
For example, the screenshot shows a tag rule where only those Virtual Machines, Virtual Machine Scale Sets, and App Service Plans tagged as Datadog = True send metrics to Datadog.
There are two types of logs that can be emitted from Azure to Datadog.
Subscription level logs - Provide insight into the operations on your resources at the control plane. Updates on service health events are also included. Use the activity log to determine the what, who, and when for any write operations (PUT, POST, DELETE). There's a single activity log for each Azure subscription.
Azure resource logs - Provide insight into operations that were taken on an Azure resource at the data plane. For example, getting a secret from a Key Vault is a data plane operation. Or, making a request to a database is also a data plane operation. The content of resource logs varies by the Azure service and resource type.
To send subscription level logs to Datadog, select Send subscription activity logs. If this option is left unchecked, none of the subscription level logs are sent to Datadog.
To send Azure resource logs to Datadog, select Send Azure resource logs for all defined resources. The types of Azure resource logs are listed in Azure Monitor Resource Log categories. To filter the set of Azure resources sending logs to Datadog, use Azure resource tags.
The logs sent to Datadog are charged by Azure. For more information, see the pricing of platform logs sent to Azure Marketplace partners.
Once you have completed configuring metrics and logs, select Next: Single sign-on.
Configure single sign-on
If you're linking the Datadog resource to an existing Datadog organization, you can't set up single sign-on at this step. Instead, you set up single sign-on after creating the Datadog resource. For more information, see Reconfigure single sign-on.
Select Next: Tags.
Add custom tags
You can specify custom tags for the new Datadog resource. Provide name and value pairs for the tags to apply to the Datadog resource.
When you've finished adding tags, select Next: Review+Create.
Review + Create Datadog resource
Review your selections and the terms of use. After validation completes, select Create.
Azure deploys the Datadog resource.
When the process completes, select Go to Resource to see the Datadog resource.
No comments:
Post a Comment