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
logger.Warn("Configuring default database from CLI parameters is deprecated. Use of the '--config.file' argument is preferred. See https://github.com/oracle/oracle-db-appdev-monitoring?tab=readme-ov-file#standalone-binary")
203
+
logger.Warn("Configuring default database from CLI parameters is deprecated. Use of the '--config.file' argument is preferred. See https://oracle.github.io/oracle-db-appdev-monitoring/docs/getting-started/basics#standalone-binary")
Copy file name to clipboardExpand all lines: site/docs/configuration/config-file.md
+16-2Lines changed: 16 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
-
title: Exporter Config File
2
+
title: Exporter Configuration
3
3
sidebar_position: 1
4
4
---
5
5
6
-
# Exporter Config File
6
+
# Exporter Configuration
7
7
8
8
The recommended way to configure the exporter is with the `--config.file` argument, specifying a YAML configuration file.
9
9
@@ -92,6 +92,20 @@ log:
92
92
# configFile: /path/to/webconfigfile
93
93
```
94
94
95
+
### Scrape on request vs. Scrape on interval
96
+
97
+
The metrics exporter has two scraping modes: scrape on request, and scrape on interval. By default, the metrics exporter scrapes metrics on request, when the `/metrics` endpoint is invoked.
98
+
99
+
To scrape metrics on a given interval, set the `metrics.scrapeInterval` property to a valid interval:
100
+
101
+
```yaml
102
+
metrics:
103
+
# Metrics will be scraped every 30s.
104
+
scrapeInterval: 30s
105
+
```
106
+
107
+
An individual metric may have its own scrape interval separate from the exporter's scrape interval. See the [metric schema](custom-metrics.md#metric-schema) for details on configuring per-metric scrape intervals.
108
+
95
109
### Config file in a container image
96
110
97
111
To add your custom config file to a container image, you can layer the base exporter image and include that config:
Copy file name to clipboardExpand all lines: site/docs/configuration/custom-metrics.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ Metrics files must contain a series of `[[metric]]` definitions, in TOML, or the
38
38
| request | Oracle database query to run for metrics scraping | String | Yes | |
39
39
| ignorezeroresult | Whether or not an error will be printed if the request does not return any results | Boolean | No | false |
40
40
| querytimeout | Oracle Database query timeout duration, e.g., 300ms, 0.5h | String duration | No | Value of query.timeout in seconds |
41
-
| scrapeinterval | Custom metric scrape interval, used if scrape.interval is provided, otherwise metrics are always scraped on request. | String duration | No | |
41
+
| scrapeinterval | Custom metric scrape interval. If the metric was already scraped during the specified interval, a cached value is provided. | String duration | No | |
42
42
| databases | Array of databases the metric will be scraped from, using the database name from the exporter config file. If not present, the metric is scraped from all databases. If the databases array is empty (`databases = []`) the metric will not be scraped, effectively being disabled. | Array of Strings | No | |
Copy file name to clipboardExpand all lines: site/docs/releases/changelog.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,14 +15,17 @@ Our current priorities to support metrics for advanced database features and use
15
15
- Standardize multi-arch builds and document supported database versions.
16
16
- Metrics with an empty databases array (`databases = []`) are now considered disabled, and will not be scraped.
17
17
- Increased the default query timeout for the `top_sql` metric to 10 seconds (previously 5 seconds).
18
+
- Metrics using the `scrapeinterval` property will no longer be scraped on every request if they have a cached value. This only applies when the metrics exporter is configured to scrape metrics _on request_, rather than on a global interval.
18
19
- Metrics using the `fieldtoappend` property now support labels. The `wait_time` and `activity` default metrics use the `fieldtoappend` property, and now properly display their labels.
19
20
- Fix `wait_time` default metric to work with Oracle Database 19c.
21
+
- Fix an issue where the exporter would unnecessarily scrape metrics with a custom scrape interval.
20
22
21
23
Thank you to the following people for their suggestions and contributions:
0 commit comments