Skip to content

Commit f200f57

Browse files
technovangelisttechnovangelist
committed
more metrics pulled from metadata
1 parent 6f94af7 commit f200f57

36 files changed

+170
-628
lines changed

‎content/integrations/etcd.md

Lines changed: 4 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
title: Datadog-etcd Integration
33
integration_title: etcd
44
kind: integration
5+
git_integration_title: etcd
56
---
67

78
### Overview
@@ -19,36 +20,10 @@ From the open-source Agent:
1920

2021

2122

22-
The following metrics are collected by default with the etcd integration:
23+
## Metrics
2324

24-
etcd.store.gets.success
25-
etcd.store.gets.fail
26-
etcd.store.sets.success
27-
etcd.store.sets.fail
28-
etcd.store.delete.success
29-
etcd.store.delete.fail
30-
etcd.store.update.success
31-
etcd.store.update.fail
32-
etcd.store.create.success
33-
etcd.store.create.fail
34-
etcd.store.compareandswap.success
35-
etcd.store.compareandswap.fail
36-
etcd.store.compareanddelete.success
37-
etcd.store.compareanddelete.fail
38-
etcd.store.expire.count
39-
etcd.store.watchers
40-
etcd.self.recv.appendrequest.count
41-
etcd.self.send.appendrequest.count
42-
43-
Plus the following metrics for leader nodes (note that these values will be undefined for single-member clusters):
44-
45-
etcd.self.send.pkgrate
46-
etcd.self.send.bandwidthrate
47-
48-
And these metrics for follower nodes:
49-
50-
etcd.self.recv.pkgrate
51-
etcd.self.recv.bandwidthrate
25+
<%= get_metrics_from_git()
26+
%>
5227

5328
Furthermore, etcd metrics are tagged with `etcd_state:leader` or `etcd_state:follower`, depending on the node status, so you can easily aggregate metrics by status.
5429

‎content/integrations/expressjs.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: Datadog-ExpressJS Integration
33
integration_title: ExpressJS
44
kind: integration
55
doclevel: basic
6+
git_integration_title: express
67
---
78

89

@@ -12,3 +13,6 @@ Add the connect-datadog middleware to your application to:
1213
* Alert on your response times
1314
* Monitor your response code
1415

16+
## Metrics
17+
18+
<%= get_metrics_from_git() %>

‎content/integrations/fastly.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,12 @@ title: Datadog-Fastly Integration
33
integration_title: Fastly
44
kind: integration
55
doclevel: basic
6+
git_integration_title: fastly
67
---
78

89

910

1011
Connect to Fastly to:
1112

1213
See key Fastly metrics (like cache coverage and header size) in context with the rest of your Datadog metrics
14+

‎content/integrations/fluentd.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: Datadog-Fluentd Integration
33
integration_title: Fluentd
44
kind: integration
55
doclevel: basic
6+
git_integration_title: fluentd
67
---
78

89

@@ -12,3 +13,7 @@ Get metrics from Fluentd in real time to
1213

1314
* Visualize Fluentd performance.
1415
* Correlate the performance of Fluentd with the rest of your applications.
16+
17+
## Metrics
18+
19+
<%= get_metrics_from_git() %>

‎content/integrations/gae.md

Lines changed: 3 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
title: Datadog-Google App Engine Integration
33
integration_title: Google App Engine
44
kind: integration
5+
git_integration_title: google_app_engine
56
---
67

78

@@ -104,40 +105,8 @@ For Python apps, you might use the dogapi library. Here is the Getting Started F
104105

105106
### Metrics
106107

107-
Upon installation of the integration you get a number of metrics before instrumenting your app.
108-
109-
* gae.memcache.byte_hits
110-
* gae.memcache.bytes
111-
* gae.memcache.hits
112-
* gae.memcache.items
113-
* gae.memcache.misses
114-
* gae.memcache.oldest_item_age
115-
* gae.requests.cost.95percentile
116-
* gae.requests.cost.avg
117-
* gae.requests.cost.count
118-
* gae.requests.cost.max
119-
* gae.requests.cost.min
120-
* gae.requests.latency.95percentile
121-
* gae.requests.latency.avg
122-
* gae.requests.latency.count
123-
* gae.requests.latency.max
124-
* gae.requests.latency.min
125-
* gae.requests.mcycles.95percentile
126-
* gae.requests.mcycles.avg
127-
* gae.requests.mcycles.count
128-
* gae.requests.mcycles.max
129-
* gae.requests.mcycles.min
130-
* gae.requests.pending_time.95percentile
131-
* gae.requests.pending_time.avg
132-
* gae.requests.pending_time.count
133-
* gae.requests.pending_time.max
134-
* gae.requests.pending_time.min
135-
* gae.requests.response_size.95percentile
136-
* gae.requests.response_size.avg
137-
* gae.requests.response_size.count
138-
* gae.requests.response_size.max
139-
* gae.requests.response_size.min
140-
* gae.task_queue.tasks
108+
<%= get_metrics_from_git() %>
109+
141110

142111

143112
-------------------------

‎content/integrations/gcp.md

Lines changed: 3 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
title: Datadog-Google Cloud Platform Integration
33
integration_title: Google Cloud Platform
44
kind: integration
5+
git_integration_title: google_cloud_platform
56
---
67

78
### Overview
@@ -16,49 +17,9 @@ Connect to Google Cloud Platform to:
1617

1718
From the Integrations page in the Datadog app, select the Google Cloud Platform tile. Switch to the **Configuration** tab and click the **Sign in with Google** button. After you allow access you can add the Project you wish to monitor. Enter the Project ID for each project. The Project ID is the multi-word id and not the Project Number.
1819

19-
### Metrics Collected
20+
### Metrics
2021

21-
The following metrics are collected from the Google Cloud Platform
22-
23-
* gcp.gce.instance.is_running
24-
* gcp.gce.project.quota.backend_services.limit
25-
* gcp.gce.project.quota.backend_services.usage
26-
* gcp.gce.project.quota.firewalls.limit
27-
* gcp.gce.project.quota.firewalls.usage
28-
* gcp.gce.project.quota.forwarding_rules.limit
29-
* gcp.gce.project.quota.forwarding_rules.usage
30-
* gcp.gce.project.quota.health_checks.limit
31-
* gcp.gce.project.quota.health_checks.usage
32-
* gcp.gce.project.quota.images.limit
33-
* gcp.gce.project.quota.images.usage
34-
* gcp.gce.project.quota.in_use_addresses.limit
35-
* gcp.gce.project.quota.in_use_addresses.usage
36-
* gcp.gce.project.quota.instance_templates.limit
37-
* gcp.gce.project.quota.instance_templates.usage
38-
* gcp.gce.project.quota.networks.limit
39-
* gcp.gce.project.quota.networks.usage
40-
* gcp.gce.project.quota.routes.limit
41-
* gcp.gce.project.quota.routes.usage
42-
* gcp.gce.project.quota.snapshots.limit
43-
* gcp.gce.project.quota.snapshots.usage
44-
* gcp.gce.project.quota.ssl_certificates.limit
45-
* gcp.gce.project.quota.ssl_certificates.usage
46-
* gcp.gce.project.quota.static_addresses.limit
47-
* gcp.gce.project.quota.static_addresses.usage
48-
* gcp.gce.project.quota.target_http_proxies.limit
49-
* gcp.gce.project.quota.target_http_proxies.usage
50-
* gcp.gce.project.quota.target_https_proxies.limit
51-
* gcp.gce.project.quota.target_https_proxies.usage
52-
* gcp.gce.project.quota.target_instances.limit
53-
* gcp.gce.project.quota.target_instances.usage
54-
* gcp.gce.project.quota.target_pools.limit
55-
* gcp.gce.project.quota.target_pools.usage
56-
* gcp.gce.project.quota.target_vpn_gateways.limit
57-
* gcp.gce.project.quota.target_vpn_gateways.usage
58-
* gcp.gce.project.quota.url_maps.limit
59-
* gcp.gce.project.quota.url_maps.usage
60-
* gcp.gce.project.quota.vpn_tunnels.limit
61-
* gcp.gce.project.quota.vpn_tunnels.usage
22+
<%= get_metrics_from_git() %>
6223

6324

6425
### Tags Assigned

‎content/integrations/gearman.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
title: Datadog-Gearman Integration
33
integration_title: Gearman
44
kind: integration
5+
git_integration_title: gearman
56
---
67

78
### Overview
@@ -18,12 +19,10 @@ From the open-source Agent:
1819
* [ Gearman checks.d][2]
1920

2021

21-
The following metrics are collected by default with the Gearman integration:
22+
### Metrics
23+
24+
<%= get_metrics_from_git() %>
2225

23-
gearman.queued
24-
gearman.running
25-
gearman.unique_tasks
26-
gearman.workers
2726

2827

2928
[1]: https://github.com/DataDog/dd-agent/blob/master/conf.d/gearmand.yaml.example

‎content/integrations/goexpvar.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: Datadog-Go Expvar Integration
33
integration_title: Go Expvar
44
kind: integration
55
doclevel: basic
6+
git_integration_title: go_expvar
67
---
78

89

@@ -12,3 +13,7 @@ Use the Datadog Expvar Agent check to:
1213
* Get information and monitor into your application memory usage
1314
* Instrument your own metrics
1415
* An example configration file for GO Expvar can be found [here](https://github.com/DataDog/dd-agent/blob/master/conf.d/go_expvar.yaml.example)
16+
17+
## Metrics
18+
19+
<%= get_metrics_from_git() %>

‎content/integrations/gunicorn.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
title: Datadog-Gunicorn Integration
33
integration_title: gunicorn
44
kind: integration
5+
git_integration_title: gunicorn
56
---
67

78
To capture Gunicorn metrics you need to install the Datadog Agent.
@@ -30,3 +31,7 @@ Edit conf.d/gunicorn.yaml
3031
- Collected 8 metrics & 0 events
3132

3233
Not sure how to execute the last two steps? Visit the Agent Usage Guide for more detailed instructions.
34+
35+
## Metrics
36+
37+
<%= get_metrics_from_git() %>

‎content/integrations/haproxy.md

Lines changed: 3 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
title: Datadog-HAProxy Integration
33
integration_title: HAProxy
44
kind: integration
5+
git_integration_title: haproxy
56
---
67

78
### Overview
@@ -24,52 +25,9 @@ From the open-source Agent:
2425

2526

2627

28+
## Metrics
2729

28-
29-
The following metrics are collected by default with the HAProxy integration:
30-
31-
haproxy.frontend.bytes.in_rate
32-
haproxy.frontend.bytes.out_rate
33-
haproxy.frontend.denied.req_rate
34-
haproxy.frontend.denied.resp_rate
35-
haproxy.frontend.errors.req_rate
36-
haproxy.frontend.requests.rate
37-
haproxy.frontend.response.1xx
38-
haproxy.frontend.response.2xx
39-
haproxy.frontend.response.3xx
40-
haproxy.frontend.response.4xx
41-
haproxy.frontend.response.5xx
42-
haproxy.frontend.response.other
43-
haproxy.frontend.session.current
44-
haproxy.frontend.session.limit
45-
haproxy.frontend.session.pct
46-
haproxy.frontend.session.time
47-
48-
haproxy.backend.bytes.in_rate
49-
haproxy.backend.bytes.out_rate
50-
haproxy.backend.connect.time
51-
haproxy.backend.denied.req_rate
52-
haproxy.backend.denied.resp_rate
53-
haproxy.backend.errors.con_rate
54-
haproxy.backend.errors.resp_rate
55-
haproxy.backend.queue.current
56-
haproxy.backend.queue.time
57-
haproxy.backend.response.1xx
58-
haproxy.backend.response.2xx
59-
haproxy.backend.response.3xx
60-
haproxy.backend.response.4xx
61-
haproxy.backend.response.5xx
62-
haproxy.backend.response.other
63-
haproxy.backend.response.time
64-
haproxy.backend.session.current
65-
haproxy.backend.session.limit
66-
haproxy.backend.session.pct
67-
haproxy.backend.session.rate
68-
haproxy.backend.session.time
69-
haproxy.backend.warnings.redis_rate
70-
haproxy.backend.warnings.retr_rate
71-
72-
30+
<%= get_metrics_from_git() %>
7331

7432
[1]: https://github.com/DataDog/dd-agent/blob/master/conf.d/haproxy.yaml.example
7533
[2]: https://github.com/DataDog/dd-agent/blob/master/checks.d/haproxy.py

0 commit comments

Comments
 (0)