Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-975

Retire JMX Endpoints

    XMLWordPrintable

Details

    • Epic
    • Resolution: Done
    • Major
    • 2023-07-24 - API
    • None
    • None
    • swatch-retire-jmx
    • False
    • Hide

      None

      Show
      None
    • False
    • Done
    • 100
    • 100% 100%

    Description

      In order to move away from using JMX for support operations.

      This will happen in phases:

      • Implement alternative HTTP APIs
      • Update QE automation to use alternative HTTP APIs
      • Get Teamnado to move to the new non-jmx api for opt-in
      • Remove the unused JMX API

      The plan for Which items to keep & why can be found at https://docs.google.com/spreadsheets/d/1zwHxQ49Fzm-2zWyIJH5qDhRlhXe0uCL7woJ2dMcsoc8/edit#gid=0

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SWATCH-714 Update to spring boot 3.x & Quarkus 3.x

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Activity

            People

              Unassigned Unassigned
              khowell@redhat.com Kevin Howell
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: