Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-4801

Monitoring resources for debugging specific components

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • 3scale Operator
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • ?

      Some suggestions from the support team regarding monitoring that would be helpful for troubleshooting customer issues. These can each be useful for both support and customers.

      Queues

      • backend-worker (doesn't seem to be any way for us to monitor this currently and in fact this would have value for the customer in case they needed to scale up replicas)
      • system-sidekiq (currently there is only the UI and rails console access, we could publish the sidekiq API and monitor those endpoints. Again this would bring value to customer also)

      Internal requests

      • There is an internal API on backend which system uses and it could be useful to monitor failed requests which would indicate data inconsistency (failure to synchronise data from system to backend)
      • Zync makes outbound requests to an OpenID Connect provider server which can result in failures (this one is actually more useful for customers to monitor than for support to use for debugging)

              Unassigned Unassigned
              rhn-support-keprice Kevin Price
              Marian Ganisin Marian Ganisin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: