Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-22245

MP Metrics configuration uses 'wildfly' as the metrics prefix

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • EAP-XP-3.0.0.CR2
    • EAP-XP-3.0.0.CR1
    • MP Metrics
    • None

    Description

      The XP3 CR1 standalone-microprofile-[ha].xml files use this config for MP Metrics:

      <subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/>

      Wrong default prefix 'wildfly'; in XP2 it is the correct 'jboss':

      <subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:jboss}"/>

      This was a porting error when creating the XP3 branch.

      Attachments

        Issue Links

          relates to

          Task - Represents a small unit of work that is not end-user facing. WFLY-15048 Microprofile testsuite should dynamically determine the expected MP Metrics vendor metric prefix

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Fabio Burzigotti Fabio Burzigotti
              Fabio Burzigotti Fabio Burzigotti
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: