Datadog
Visualize Datadog services and users, and monitor changes to Datadog users through queries and alerts.
- Installation
- Data Model
- Types
Installation
Before setting up the integration within JupiterOne, you will need to create an API key and Application key in Datadog.
- To create your API key: navigate to your Datadog organization's API keys and select New Key.
Your account must have the Datadog Admin Role to generate an API key.
- To create an application key: navigate to your Datadog organization's application keys and select New Key. Required scopes:
user_access_readhosts_readorg_management
Configuration in JupiterOne
To install the Datadog integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Datadog. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
The Account Name used to identify the Datadog account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen theAccountNametoggle is enabled. -
Description to assist in identifying the integration instance, if desired.
-
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration. -
Your Datadog API Key, Application Key, and your Datadog email (the email associated with your Datadog account).
-
Optionally, enter the Datadog Host and Datadog Organization ID for your organization. You can find this by sending a GET request to the endpoint listed at https://docs.datadoghq.com/api/latest/organizations/#list-your-managed-organizations.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Account | datadog_account | Account |
| Host | datadog_host | Host |
| Role | datadog_role | AccessRole |
| User | datadog_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
datadog_account | HAS | datadog_user |
datadog_account | HAS | datadog_role |
datadog_account | HAS | datadog_host |
datadog_user | ASSIGNED | datadog_role |
Datadog Account
datadog_account inherits from Account
Datadog Host
datadog_host inherits from Host
| Property | Type | Description | Specifications |
|---|---|---|---|
agentVersion | string | ||
aliases | array of strings | ||
apps | array of strings | ||
awsName | string | ||
hostCpuCores | number | ||
id * | string | ||
isMuted | boolean | ||
machine | string | ||
name | string | ||
platform | string | ||
processor | string | ||
pythonVersion | string | ||
reportedOn | number | ||
socketFqdn | string | ||
socketHostname | string | ||
sources | array of strings | ||
state | string |
Datadog Role
datadog_role inherits from AccessRole
| Property | Type | Description | Specifications |
|---|---|---|---|
createdAt | number | ||
modifiedAt | number | ||
userCount | number |
Datadog User
datadog_user inherits from User
| Property | Type | Description | Specifications |
|---|---|---|---|
disabled | boolean | ||
icon | string | ||
verified | boolean |