Uploaded image for project: 'JBoss Web Server'
  1. JBoss Web Server
  2. JWS-3755

[Operator] JWS image switch to UBI9

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • Operator.2.3.0.GA
    • None
    • operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      UBI 9 image does not offer 'prometheus-jmx-exporter' package which causes a problem for operator.

      Copied from mail conversation:
      1. Removing prometheus-jmx-exporter from the JWS Image

      While this isn't primarily an operator issue, it significantly impacts the operator's behavior regarding metric collection. Let's discuss different operator scenarios and potential solutions:

      a) Operator works with a user-provided application image:

      In this case, we have no control. The user remains fully responsible for exporting JMX metrics.

      b) Operator builds the image containing the user's application:

      We can leverage the JFC-created JMX-Exporter Servlet and deploy it alongside the user's application.

      The operator will provide a configuration option allowing the user to explicitly enable or disable the JMX-Exporter Servlet integration.

      Next step: Should I begin investigating the technical details of injecting the JMX-Exporter Servlet into the image-building process?

              mmadzin@redhat.com Matus Madzin
              mmadzin@redhat.com Matus Madzin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: