Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11529

Expose WildFly metrics in /metrics endpoints

    Details

      Description

      MicroProfile Metrics mandates that metrics names are unique and does not able to have multiple suppliers for the same metric with different labels.
      Due to this restriction, the names of WildFly metrics are long and convoluted; e.g. `deployment/example.war/subsystem/undertow/servlet/org.example.MyServlet/request-count`

      This type of names prevents any aggregation in Prometheus and is very different from the names configured in the imx-exporter for older WildFly versions (https://github.com/jboss-openshift/cct_module/pull/314)
      Instead, the name of the metric should be "simple" (e.g. wildfly_undertow_request_count) and the different supplies should provide labels:

      wildfly_undertow_request_count_total{deployment="foo.war", servlet="MyServletA"} 5.0
      wildfly_undertow_request_count_total{deployment="foo.war", servlet="MyServletB"} 10.0
      

      The goal of this issue is to provide metrics for WildFly subsystem and deployments that follows the Prometheus convention.
      As these conventions is not compatible with MicroProfile Metrics 1.x, these metrics will only be exposed by the HTTP endpoint on /metrics in the Prometheus format (in addition to the base and vendor metrics provided through the microprofile-metrics API).

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jmesnil Jeff Mesnil
                  Reporter:
                  jmesnil Jeff Mesnil
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: