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

Do not expose WildFly metrics in /metrics endpoints

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 15.0.0.Beta1
    • Fix Version/s: 15.0.0.Final
    • Component/s: MP Metrics
    • Labels:
      None

      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. undertow_request_count) and the different supplies should provide labels:

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

      In its current state the WildFly metrics are not usable and we should disable them until they are properly exposed in a correct state.

        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: