You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/configuration.md
+52-45Lines changed: 52 additions & 45 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,23 +13,23 @@ Command-line flags are used to configure settings of the exporter which cannot b
13
13
14
14
All flags may be prefixed with either one hypen or two (i.e., both `-config.file` and `--config.file` are valid).
15
15
16
-
| Flag | Description | Default value |
17
-
| --- | --- | --- |
18
-
|`-listen-address`| Network address to listen to |`127.0.0.1:5000`|
19
-
|`-config.file`| Path to the configuration file |`config.yml`|
20
-
|`-log.format`| Output format of log messages. One of: [logfmt, json]|`json`|
21
-
|`-debug`| Log at debug level |`false`|
22
-
|`-fips`| Use FIPS compliant AWS API |`false`|
23
-
|`-cloudwatch-concurrency`| Maximum number of concurrent requests to CloudWatch API |`5`|
24
-
|`-cloudwatch-concurrency.per-api-limit-enabled`| Enables a concurrency limiter, that has a specific limit per CloudWatch API call. |`false`|
25
-
|`-cloudwatch-concurrency.list-metrics-limit`| Maximum number of concurrent requests to CloudWatch `ListMetrics` API. Only applicable if `per-api-limit-enabled` is `true`. |`5`|
26
-
|`-cloudwatch-concurrency.get-metric-data-limit`| Maximum number of concurrent requests to CloudWatch `GetMetricsData` API. Only applicable if `per-api-limit-enabled` is `true`. |`5`|
27
-
|`-cloudwatch-concurrency.get-metric-statistics-limit`| Maximum number of concurrent requests to CloudWatch `GetMetricStatistics` API. Only applicable if `per-api-limit-enabled` is `true`. |`5`|
28
-
|`-tag-concurrency`| Maximum number of concurrent requests to Resource Tagging API |`5`|
29
-
|`-scraping-interval`| Seconds to wait between scraping the AWS metrics |`300`|
30
-
|`-metrics-per-query`| Number of metrics made in a single GetMetricsData request |`500`|
31
-
|`-labels-snake-case`| Output labels on metrics in snake case instead of camel case |`false`|
32
-
|`-profiling.enabled`| Enable the /debug/pprof endpoints for profiling |`false`|
|`-listen-address`| Network address to listen to|`127.0.0.1:5000`|
19
+
|`-config.file`| Path to the configuration file |`config.yml`|
20
+
|`-log.format`| Output format of log messages. One of: [logfmt, json]|`json`|
21
+
|`-debug`| Log at debug level |`false`|
22
+
|`-fips`| Use FIPS compliant AWS API |`false`|
23
+
|`-cloudwatch-concurrency`| Maximum number of concurrent requests to CloudWatch API |`5`|
24
+
|`-cloudwatch-concurrency.per-api-limit-enabled`| Enables a concurrency limiter, that has a specific limit per CloudWatch API call. |`false`|
25
+
|`-cloudwatch-concurrency.list-metrics-limit`| Maximum number of concurrent requests to CloudWatch `ListMetrics` API. Only applicable if `per-api-limit-enabled` is `true`. |`5`|
26
+
|`-cloudwatch-concurrency.get-metric-data-limit`| Maximum number of concurrent requests to CloudWatch `GetMetricsData` API. Only applicable if `per-api-limit-enabled` is `true`. |`5`|
27
+
|`-cloudwatch-concurrency.get-metric-statistics-limit`| Maximum number of concurrent requests to CloudWatch `GetMetricStatistics` API. Only applicable if `per-api-limit-enabled` is `true`. |`5`|
28
+
|`-tag-concurrency`| Maximum number of concurrent requests to Resource Tagging API |`5`|
29
+
|`-scraping-interval`| Seconds to wait between scraping the AWS metrics |`300`|
30
+
|`-metrics-per-query`| Number of metrics made in a single GetMetricsData request |`500`|
31
+
|`-labels-snake-case`| Output labels on metrics in snake case instead of camel case |`false`|
32
+
|`-profiling.enabled`| Enable the /debug/pprof endpoints for profiling |`false`|
33
33
34
34
## YAML configuration file
35
35
@@ -91,8 +91,8 @@ type: <string>
91
91
roles:
92
92
[ - <role_config> ... ]
93
93
94
-
# List of Key/Value pairs to use for tag filtering (all must match).
95
-
# The key is the AWS Tag key and is case-sensitive
94
+
# List of Key/Value pairs to use for tag filtering (all must match).
95
+
# The key is the AWS Tag key and is case-sensitive
96
96
# The value will be treated as a regex
97
97
searchTags:
98
98
[ - <search_tags_config> ... ]
@@ -114,7 +114,7 @@ dimensionNameRequirements:
114
114
# This is useful for reducing the number of metrics returned by CloudWatch, which can be very large for some services. See AWS Cloudwatch API docs for [ListMetrics](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_ListMetrics.html) for more details.
115
115
[ recentlyActiveOnly: <boolean> ]
116
116
117
-
# Can be used to include contextual information (account_id, region, and customTags) on info metrics and cloudwatch metrics. This can be particularly
117
+
# Can be used to include contextual information (account_id, region, and customTags) on info metrics and cloudwatch metrics. This can be particularly
118
118
# useful when cloudwatch metrics might not be present or when using info metrics to understand where your resources exist
119
119
[ includeContextOnInfoMetrics: <boolean> ]
120
120
@@ -137,6 +137,11 @@ statistics:
137
137
# Export the metric with the original CloudWatch timestamp (General Setting for all metrics in this job)
138
138
[ addCloudwatchTimestamp: <boolean> ]
139
139
140
+
# Include any metrics in the past if they are present in the CloudWatch metric response. This is useful, for example, if a metric is setup with
141
+
# period 60s and length 300s so all the 5 data points are exposed in the metrics endpoint and not just the last one
142
+
# (General Setting for all metrics in this job)
143
+
[ addHistoricalMetrics: <boolean> ]
144
+
140
145
# List of metric definitions
141
146
metrics:
142
147
[ - <metric_config> ... ]
@@ -152,18 +157,18 @@ discovery:
152
157
kafka:
153
158
- Name
154
159
jobs:
155
-
- type: kafka
156
-
regions:
157
-
- eu-west-1
158
-
searchTags:
159
-
- key: env
160
-
value: dev
161
-
metrics:
162
-
- name: BytesOutPerSec
163
-
statistics:
164
-
- Average
165
-
period: 600
166
-
length: 600
160
+
- type: kafka
161
+
regions:
162
+
- eu-west-1
163
+
searchTags:
164
+
- key: env
165
+
value: dev
166
+
metrics:
167
+
- name: BytesOutPerSec
168
+
statistics:
169
+
- Average
170
+
period: 600
171
+
length: 600
167
172
```
168
173
169
174
### `static_job_config`
@@ -178,23 +183,19 @@ name: <string>
178
183
namespace: <string>
179
184
180
185
# List of AWS regions
181
-
regions:
182
-
[ - <string> ...]
186
+
regions: [- <string> ...]
183
187
184
188
# List of IAM roles to assume (optional)
185
-
roles:
186
-
[ - <role_config> ... ]
189
+
roles: [- <role_config> ...]
187
190
188
191
# Custom tags to be added as a list of Key/Value pairs
189
-
customTags:
190
-
[ - <custom_tags_config> ... ]
192
+
customTags: [- <custom_tags_config> ...]
191
193
192
194
# CloudWatch metric dimensions as a list of Name/Value pairs
193
-
dimensions: [<dimensions_config>]
195
+
dimensions: [<dimensions_config>]
194
196
195
197
# List of metric definitions
196
-
metrics:
197
-
[ - <metric_config> ... ]
198
+
metrics: [- <metric_config> ...]
198
199
```
199
200
200
201
Example config file:
@@ -208,15 +209,15 @@ static:
208
209
regions:
209
210
- eu-west-1
210
211
dimensions:
211
-
- name: AutoScalingGroupName
212
-
value: MyGroup
212
+
- name: AutoScalingGroupName
213
+
value: MyGroup
213
214
customTags:
214
215
- key: CustomTag
215
216
value: CustomValue
216
217
metrics:
217
218
- name: GroupInServiceInstances
218
219
statistics:
219
-
- Minimum
220
+
- Minimum
220
221
period: 60
221
222
length: 300
222
223
```
@@ -276,6 +277,11 @@ statistics:
276
277
# Export the metric with the original CloudWatch timestamp (General Setting for all metrics in this job)
277
278
[ addCloudwatchTimestamp: <boolean> ]
278
279
280
+
# Include any metrics in the past if they are present in the CloudWatch metric response. This is useful, for example, if a metric is setup with
281
+
# period 60s and length 300s so all the 5 data points are exposed in the metrics endpoint and not just the last one
- Watch out using `addCloudwatchTimestamp` for sparse metrics, e.g from S3, since Prometheus won't scrape metrics containing timestamps older than 2-3 hours.
348
+
- Watch out using `addCloudwatchTimestamp` for sparse metrics, e.g from S3, since Prometheus won't scrape metrics containing timestamps older than 2-3 hours. Also the same applies when enabling `addHistoricalMetrics` in any metric
0 commit comments