[jira] [Created] (IMPALA-8799) Prometheus metrics should be prefixed with "impala_"

["Tim Armstrong (JIRA)" <ji...@apache.org>]

Tim Armstrong created IMPALA-8799:
-------------------------------------

             Summary: Prometheus metrics should be prefixed with "impala_"
                 Key: IMPALA-8799
                 URL: https://issues.apache.org/jira/browse/IMPALA-8799
             Project: IMPALA
          Issue Type: Improvement
          Components: Backend
            Reporter: Tim Armstrong
            Assignee: Tim Armstrong


This is recommended by the Prometheus docs - https://prometheus.io/docs/practices/naming/

{quote}
A metric name...

    ...must comply with the data model for valid characters.
    ...should have a (single-word) application prefix relevant to the domain the metric belongs to. The prefix is sometimes referred to as namespace by client libraries. For metrics specific to an application, the prefix is usually the application name itself. Sometimes, however, metrics are more generic, like standardized metrics exported by client libraries. Examples:
        prometheus_notifications_total (specific to the Prometheus server)
        process_cpu_seconds_total (exported by many client libraries)
        http_request_duration_seconds (for all HTTP requests)
{quote}

It is also awkward in tools like grafana to find impala metrics with the current naming scheme.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)