If you use Datadog to monitor your resources, then you can take advantage of Cloudability's Datadog integration to help you reduce wasted spend by optimizing your resource usage. Cloudability uses your Datadog credentials to ingest utilization metrics and generate accurate rightsizing recommendations for the following types of cloud computing resources across all your Datadog organizational accounts:
- AWS EC2
- Azure Compute (requires subscription integration)
Additionally, we support the following Datadog capabilities:
Using an Application Performance Monitoring (APM) product like Datadog makes it easy to generate and collect the necessary resource utilization metrics (such as guest memory metrics, which can be difficult to instrument at scale) to get an accurate picture of how the resource is being utilized leading to an accurate rightsizing recommendation. Learn more about Datadog and its product offerings here.
API and Application keys
Through Datadog, create an API key and Application key for use in Cloudability. If you have multiple Datadog organizations, then create one API key and Application key per organization. Cloudability requires only a single API key and Application key per Datadog organizational account.
1. Create an API key
2. Create an Application Key
A note about Datadog keys and Cloudability support
Using Datadog, a user can generate keys for each of their Datadog organizational accounts. All keys within a Datadog organizational account provide access to data within that account. These keys are comprised of two components:
- API key
- Application key
Both these keys are needed in order to make requests against Datadog's APIs. As of writing this KB, Datadog has three types of Application keys that determine the level of access:
Cloudability supports all three types of Application keys listed above.
Read-only keys have the following limitations:
- Read-only keys prevent Cloudability from fetching metadata, such as key name, for the keys.
- Read-only keys prevent Cloudability from being able to perform de-dup. For example, in the case when a user adds multiple read-only keys from the same Datadog organizational account: We need only a single API and Application key per account, but we can't de-dup since read-only keys do not provide us access to the data necessary to perform that check. In other words, Cloudability does not know that these read-only credentials are from the same account.
1. Navigate to Home > Settings > Vendor Credentials, then click the Datadog tab:
2. Add a Datadog credential for your organizational account.
Click the "Yes, I'm ready" button and fill in the details for your Datadog organizational account.
|Organization Label||Provide a descriptive label for this organization|
Copy the API associated with your organization from here:
Copy the Application key associated with the organization here:
|Rate Limit||We assume a rate limit of 600 API requests per hour per organization. Set this number to what has been configured for your organization.|
|Datadog Site||Select either datadoghq.com or datadoghq.eu. Choose datadog.eu if your account resides in the European Union.|
3. Click the "Save" button once you're done and you should see a message saying that your Datadog credential has been successfully added.
4. Repeat this process for additional credentials
5. Add credentials for all your Datadog multiple organizational accounts.
Click on the "Add a Credential" button and follow the steps as before. Once you're done, you will see all your Datadog credentials listed on the page.
A note about Read-only credentials
A read-only Application key from Datadog prevents Cloudability from fetching additional data about the API and Application key.
In those cases, metadata about the keys (such as key name, owner, etc.) will be marked as Not Available.
Additionally, if there are multiple such read-only credentials then Cloudability cannot guarantee that no duplicates exist (providing access to the same data) since the de-dup logic does not fully work with read-only keys.