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
|`google.project-id`| No | GCloud SDK auto-discovery | Comma seperated list of Google Project IDs |
82
82
|`monitoring.metrics-ingest-delay`| No || Offsets metric collection by a delay appropriate for each metric type, e.g. because bigquery metrics are slow to appear |
83
-
| `monitoring.drop-delegated-projects| No | No | Drop metrics from attached projects and fetch `project_id` only. |
84
-
|`monitoring.metrics-type-prefixes`| Yes || Comma separated Google Stackdriver Monitoring Metric Type prefixes (see [example][metrics-prefix-example] and [available metrics][metrics-list]) |
83
+
|`monitoring.drop-delegated-projects`| No | No | Drop metrics from attached projects and fetch `project_id` only.|
84
+
|`monitoring.metrics-type-prefixes`| Yes || Comma separated Google Stackdriver Monitoring Metric Type prefixes (see [example][metrics-prefix-example] and [available metrics][metrics-list]) |
85
85
|`monitoring.metrics-interval`| No |`5m`| Metric's timestamp interval to request from the Google Stackdriver Monitoring Metrics API. Only the most recent data point is used |
86
-
|`monitoring.metrics-offset`| No |`0s`| Offset (into the past) for the metric's timestamp interval to request from the Google Stackdriver Monitoring Metrics API, to handle latency in published metrics |
86
+
|`monitoring.metrics-offset`| No |`0s`| Offset (into the past) for the metric's timestamp interval to request from the Google Stackdriver Monitoring Metrics API, to handle latency in published metrics |
87
87
|`monitoring.filters`| No || Formatted string to allow filtering on certain metrics type |
88
88
|`monitoring.aggregate-deltas`| No || If enabled will treat all DELTA metrics as an in-memory counter instead of a gauge. Be sure to read [what to know about aggregating DELTA metrics](#what-to-know-about-aggregating-delta-metrics)|
89
89
|`monitoring.aggregate-deltas-ttl`| No |`30m`| How long should a delta metric continue to be exported and stored after GCP stops producing it. Read [slow moving metrics](#slow-moving-metrics) to understand the problem this attempts to solve |
90
90
|`monitoring.descriptor-cache-ttl`| No |`0s`| How long should the metric descriptors for a prefixed be cached for |
91
-
|`stackdriver.max-retries`| No |`0`| Max number of retries that should be attempted on 503 errors from stackdriver. |
91
+
|`stackdriver.max-retries`| No |`0`| Max number of retries that should be attempted on 503 errors from stackdriver. |
92
92
|`stackdriver.http-timeout`| No |`10s`| How long should stackdriver_exporter wait for a result from the Stackdriver API. |
93
93
|`stackdriver.max-backoff=`| No || Max time between each request in an exp backoff scenario. |
94
-
|`stackdriver.backoff-jitter`| No | `1s | The amount of jitter to introduce in a exp backoff scenario. |
94
+
|`stackdriver.backoff-jitter`| No |`1s`| The amount of jitter to introduce in a exp backoff scenario.|
95
95
|`stackdriver.retry-statuses`| No |`503`| The HTTP statuses that should trigger a retry. |
96
-
|`web.config.file`| No ||[EXPERIMENTAL] Path to configuration file that can enable TLS or authentication. |
96
+
|`web.config.file`| No ||[EXPERIMENTAL] Path to configuration file that can enable TLS or authentication. |
97
97
|`web.listen-address`| No |`:9255`| Address to listen on for web interface and telemetry Repeatable for multiple addresses. |
98
98
|`web.systemd-socket`| No || Use systemd socket activation listeners instead of port listeners (Linux only). |
99
-
|`web.stackdriver-telemetry-path`| No |"/metrics"| Path under which to expose Stackdriver metrics. |
99
+
|`web.stackdriver-telemetry-path`| No |`/metrics`| Path under which to expose Stackdriver metrics. |
100
100
|`web.telemetry-path`| No |`/metrics`| Path under which to expose Prometheus metrics |
0 commit comments