Skip to content

Commit a2bd798

Browse files
isaacddisaacdd
committed
Merge branch 'master' of github.com:DataDog/documentation
2 parents e731c3a + 32c9a53 commit a2bd798

File tree

2 files changed

+88
-4
lines changed

2 files changed

+88
-4
lines changed

‎content/integrations/aws.html

Lines changed: 18 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@
119119

120120
Below is the list of events that Datadog will collect from CloudTrail and display in your event stream. If you would like to see other events that are not mentionned here, please reach out to <a href="/help">our support team</a>.
121121

122-
**EC2 Actions**<br/>
122+
*EC2 Actions**<br/>
123123
AttachVolume<br/>
124124
AuthorizeSecurityGroup<br/>
125125
CreateSecurityGroup<br/>
@@ -257,7 +257,21 @@
257257

258258
#### Metrics delayed?
259259

260-
<p>When using the AWS integration, we're pulling in metrics via the Cloudwatch API. There is a delay that can occur which is a byproduct of how we’re constrained when crawling the CloudWatch APIs. This is a limitation of AWS Cloudwatch; standard metrics are captured by AWS every 3-5 minutes, may not be exposed by the AWS Cloudwatch APIs before 10 minutes and we are then subject to API throttling when we crawl them, which can result in a slight delay. Overall, we're always looking to cut down on this delay and have a faster priority crawler currently in Beta.</p>
261260

262-
<p>For metrics with zero delay, we recommend installing the Datadog Agent on those hosts. We’ve written a bit about this here (especially in relation to CloudWatch):
263-
<a href="http://www.datadoghq.com/2013/10/dont-fear-the-agent/">www.datadoghq.com/2013/10/dont-fear-the-agent</a></p>
261+
<p>When using the AWS integration, we're pulling in metrics via the Cloudwatch API. You may
262+
see a slight delay in metrics from AWS due to some constraints that exist for their API.</p>
263+
264+
<p>To begin, the Cloudwatch API only offers a metric-by-metric crawl to pull data. The Cloudwatch
265+
APIs have a rate limit that varies based on the combination of authentication credentials, region,
266+
and service. Metrics are made available by AWS dependent on the account level. For example, if
267+
you are paying for "detailed metrics" within AWS, they are available more quickly. This level
268+
of service for detailed metrics also applies to granularity, with some metrics being
269+
available per minute and others per five minutes.</p>
270+
271+
<p>On the Datadog side, we do have the ability to prioritize certain metrics within an account
272+
to pull them in faster, depending on the circumstances. Please contact
273+
<a href="mailto:support@datadoghq.com">support@datadoghq.com</a> for more info on this.</p>
274+
275+
<p>To obtain metrics with virtually zero delay, we recommend installing the Datadog Agent on those hosts. We’ve
276+
written a bit about this <a target="_blank" href="www.datadoghq.com/2013/10/dont-fear-the-agent">here</a>,
277+
especially in relation to CloudWatch.

‎content/integrations/new_integration.html

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
---
2+
title: Officially Integrating with Datadog
3+
sidebar:
4+
nav:
5+
- header: Guides
6+
- text: Getting Started with the Agent
7+
href: "/guides/basic_agent_usage/"
8+
- text: Datadog Overview
9+
href: "/overview/"
10+
- text: Sending App Metrics
11+
href: "/guides/metrics/"
12+
- text: Log Parsing in the Agent
13+
href: "/guides/logs/"
14+
- text: Writing an Agent Check
15+
href: "/guides/agent_checks/"
16+
- text: Setting up Service Checks
17+
href: "/guides/services_checks/"
18+
- text: Deploying the Agent with Chef
19+
href: "/guides/chef/"
20+
- text: Guide to Alerting
21+
href: "/guides/alerting/"
22+
- text: Single Sign On With SAML
23+
href: "/guides/saml/"
24+
- text: Billing FAQ
25+
href: "/guides/billing/"
26+
- header: References
27+
- text: API
28+
href: "/api/"
29+
- text: Libraries
30+
href: "/libraries/"
31+
- text: Graphing
32+
href: "/graphing/"
33+
- text: Host Names
34+
href: "/hostnames/"
35+
- text: Integrations
36+
href: "/integrations/"
37+
- text: DogStatsD
38+
href: "/guides/dogstatsd/"
39+
---
40+
<p>Being able to
41+
see all of your metrics from across your infrastructure is key within Datadog.
42+
While we do have guides to submit <a target="_blank" href="http://docs.datadoghq.com/guides/metrics/">custom metrics</a>
43+
via our <a target="_blank" href="http://docs.datadoghq.com/api/">API</a>
44+
and <a target="_blank" href="http://docs.datadoghq.com/libraries/">code instrumentation</a>,
45+
it's possible you might want to see a certain source become an
46+
official integration. Overall, the largest deciding factor in what integrations
47+
we build is what our clients request.</p>
48+
49+
<p>If you would like to propose an
50+
integration, please reach out to support@datadoghq.com and tell us what metrics
51+
you would like to see from that given source.</p>
52+
53+
<p>If you manage or work with a
54+
service and would like to see Datadog integrate it, the following information
55+
is needed:</p>
56+
<ul>
57+
<li>How will data get into Datadog? There are currently three options:
58+
<ol>
59+
<li>Push data from the source to Datadog</li>
60+
<li>Crawl the data source's API</li>
61+
<li>Have the Datadog Agent pick up the information from the source</li>
62+
</ol>
63+
</li>
64+
<li>What are the metrics and tags should be picked up from the source?</li>
65+
<li>What metrics should be included on the default dashboard that we generate for each integration?</li>
66+
</ul>
67+
68+
69+
<p>We will also need a short blurb describing the integration as well as the correct
70+
image to use across our site. </p>

0 commit comments

Comments
 (0)