Mention in docs that intervals are expected to be integers

Author: 0xgouda

docs/reference/metric_definitions.md

@@ -115,8 +115,8 @@ only floats can be stored!
  extra attributes, if any (see below for options). Hit the "ADD METRIC"
  button to store.
 1. Activate the newly added metric by including it in some existing
-    *Preset Config* in the "PRESETS" page or add it directly to the monitored DB,
- together with an interval, into the "METRICS" tab when editing a source on the "SOURCES" page.
+ *Preset Config* in the "PRESETS" page or add it directly to the monitored DB,
+ together with a fetching interval - integral number of seconds - into the "METRICS" tab when editing a source on the "SOURCES" page.
 
 ### For *YAML* based setups
 

docs/tutorial/custom_installation.md

@@ -354,27 +354,24 @@ The content of a file is a array of sources definitions, like this:
 
 ```yaml
 - name: test1       # An arbitrary unique name for the monitored source
-  kind: postgres    # One of the:
+  kind: postgres    # One of:
                       # - postgres
                       # - postgres-continuous-discovery
                       # - pgbouncer
                       # - pgpool
                       # - patroni
-                      # - patroni-continuous-discovery
-                      # - patroni-namespace-discover
-                      # Defaults to postgres if not specified
   conn_str: postgresql://pgwatch:xyz@somehost/mydb
   preset_metrics: exhaustive # from list of presets defined in "metrics.yaml" or in the config DB
-  custom_metrics:    # map of metrics and intervals, if both preset_metrics and custom_metrics are specified, custom wins
-        backends: 300
+  custom_metrics:     # map of metrics and intervals, if both preset_metrics and custom_metrics are specified, preset wins
+        backends: 300 # integral number of seconds
         archiver: 120
   preset_metrics_standby: # optional preset configuration for standby state, same as preset_metrics
   custom_metrics_standby: # optional custom metrics for standby state, same as custom_metrics
   include_pattern: # regex to filter databases to actually monitor for the "continuous" modes
   exclude_pattern:
   is_enabled: true
-  group: default # just for logical grouping of DB hosts or for "sharding", i.e. splitting the workload between many gatherer daemons
-  custom_tags:      # option to add arbitrary tags for every stored data row,
-        aws_instance_id: i-0af01c0123456789a       # for example to fetch data from some other source onto a same Grafana graph
+  group: default # just for logical grouping of DB hosts or for "sharding", i.e. splitting the workload between many gatherer daemons (via --group option)
+  custom_tags:   # option to add arbitrary tags for every stored data row,
+        aws_instance_id: i-0af01c0123456789a # for example to fetch data from some other source onto a same Grafana graph
 ...
 ```