- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Use this guide to manually set up the Datadog Azure Native integration through creation of the Datadog resource in Azure.
The Datadog resource streamlines management and data collection for your Azure environment. Datadog recommends using this method when possible. This replaces the App Registration credential process used by the standard Azure integration for metric collection and Event Hub setup for log forwarding.
To set up the Azure Native integration, you must be an Owner on any Azure subscriptions you want to link, and Admin for the Datadog organization you are linking them to. Ensure you have the appropriate access before starting the setup.
Configuring the Azure integration requires the creation of a Datadog resource in Azure. These resources represent the connection or link between a Datadog organization and an Azure subscription. Multiple Azure subscriptions can be connected to Datadog with a single Datadog resource.
There are two options when you create a Datadog resource in Azure:
Link to an existing Datadog organization. This is the more common action. Use this to configure your Datadog org to monitor an Azure subscription that hasn’t been linked yet. This action does not affect your Datadog billing plan.
Create a new Datadog organization. This flow is less common. Use this if you do not yet have a Datadog org and you want to get started with a paid plan through Azure Marketplace. This flow creates a brand new Datadog org, allows you to select a billing plan, and links the associated Azure subscription for monitoring.
Note: Trials are not available through the Create a new Datadog organization option in Azure. To get started with a free trial, first create a trial Datadog org on the US3 site. Then use the linking flow to add any subscriptions you want to monitor.
Once you create a Datadog resource, data collection begins for the associated subscription. See details for using this resource to configure, manage, and deploy Datadog in the Managing the Azure Native Integration guide.
To start monitoring an Azure subscription, navigate to the Datadog Service page in Azure and select the option to create a new Datadog resource:
Choose Link Azure subscription to an existing Datadog organization or Create a new Datadog organization. Linking is the more common action. Use this to configure monitoring for an Azure subscription that hasn’t been linked yet. Only choose the Create flow if you are not yet a Datadog customer and want to get started with a new, paid plan.
Note: New Datadog organizations created through the Azure portal automatically have billing consolidated into their Azure invoice. This usage counts towards your organization’s MACC if applicable.
(Optional): You can configure single sign-on (SSO) during the process of creating a new Datadog organization in Azure. You can also configure SSO later. To configure SSO during the initial creation, first create a Datadog enterprise gallery app.
After selecting to link to an existing Datadog organization, the portal displays a form for creating the Datadog resource:
Provide the following values:
Property | Description |
---|---|
Subscription | The Azure subscription you want to monitor with Datadog. The Datadog resource exists in this subscription. You must have owner access. |
Resource group | 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. The recommended naming convention is: subscription_name-datadog_org_name . |
Location | The location is West US2—this is the location where Datadog’s US3 site is hosted in Azure. This has no impact on your use of Datadog. Like all Datadog sites, the US3 site is entirely SaaS and supports monitoring all Azure regions as well as other cloud providers and on-premises hosts. |
Datadog organization | After the authentication step is completed, the Datadog organization name is set to the name of the Datadog organization being linked. The Datadog site is set to US3. |
Click Link to Datadog organization to open a Datadog authentication window, then sign in to Datadog.
By default, Azure links your current Datadog organization to your Datadog resource. If you want to link to a different organization, select the appropriate organization in the authentication window:
When the OAuth flow is complete, verify the Datadog organization name is correct.
After selecting to create a new Datadog organization, the portal displays a form for creating both the Datadog resource and the new Datadog organization:
Provide the following values:
Property | Description |
---|---|
Subscription | The Azure subscription you want to monitor with Datadog. The Datadog resource exists in this subscription. You must have owner access. |
Resource group | 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 | The name for the Datadog resource. This name is assigned to the new Datadog organization. |
Location | The location is West US2—this is the location where Datadog’s US3 site is hosted in Azure. This has no impact on your use of Datadog. Like all Datadog sites, the US3 site is entirely SaaS and supports monitoring all Azure regions as well as other cloud providers and on-premises hosts. |
Datadog organization | The Datadog organization name is set to the resource name, and the Datadog site is set to US3. |
Pricing plan | A list of the available Datadog pricing plans. If you have a private offer, it iss available in this dropdown. |
Billing term | Monthly. |
To see a list of virtual machines (VMs) in the subscription, select Virtual machine agent in the left sidebar. On this page, you can install the Datadog Agent on a VM as an extension.
For each VM, the following information is displayed:
Column | Description |
---|---|
Resource name | The VM’s name |
Resource status | Whether the VM is stopped or running. The Datadog Agent can only be installed on a running VM. If the VM is stopped, installing the Datadog Agent is disabled. |
Agent version | The Datadog Agent version number |
Agent status | Whether the Datadog Agent is running on the VM. |
Integrations enabled | The key metrics being collected by enabled integrations in the Datadog Agent. |
Install method | The specific tool used to install the Datadog Agent, such as Chef, Azure VM extension, etc. |
Sending logs | Whether the Datadog Agent is sending logs to Datadog. |
You can install the Datadog Agent directly in Azure with the VM Extension. To install the Datadog Agent:
Installing
until the Agent is installed and provisioned. After the Datadog Agent is installed, the status changes to Installed
.If the Datadog Agent was installed with the Azure VM extension:
If the Agent was installed using a different method, you cannot use the Datadog resource to deploy or remove the Agent, but information about the Agent is still reflected on this page.
The Datadog AKS Cluster Extension allows you to deploy the Datadog Agent natively within Azure AKS, avoiding the complexity of third-party management tools.
To install the Datadog Agent with the AKS Cluster Extension:
Datadog AKS Cluster Extension
.Datadog.AKSExtension
).추가 유용한 문서, 링크 및 기사: