---

   pmdaopenmetrics    ( 1 )

---

METRIC NAMING

All metrics from a file named JOB.*  will be exported as PCP
       metrics with the openmetrics.JOB metric name prefix.  Therefore,
       the JOB name must be a valid non-leaf name for PCP PMNS metric
       names.  If the JOB name has multiple dot-separated components,
       the resulting PMNS names will include those components and care
       is needed to ensure there are no overlapping definitions, e.g.
       metrics returned by JOB.response may overlap or conflict with
       metrics returned by JOB.response.time.

       Config file entries (URLs or scripts) found in subdirectories of
       the config directory will also result in hierarchical metric
       names.  For example, a config file named
       $PCP_PMDAS_DIR/openmetrics/config.d/mysource/latency/get.url will
       result in metrics being created (by fetching that source URL)
       below openmetrics.mysource.latency.get in the PCP namespace.
       Scripts found in subdirectories of the config directory similarly
       result in hierarchical PCP metric names.