Uploaded image for project: 'CloverDX'
  1. CloverDX
  2. CLO-19414

Failing state for the Listeners

    XMLWordPrintable

    Details

    • Story Points:
      8
    • QA Testing:
      UNDECIDED
    • Sprint:
      Green Sprint 118, Green Sprint 119, Green Sprint 120

      Description

      As a L1 support (help desk) or L2 support (in-depth technical support) I want to see whether there is some issue with particular listener without a need to deep dive and study its log or tasks history.

      The history of every listener is shown in the Server UI (OK, FAIL and Last Run) but the listener itself doesn't have a state. It cannot get red and indicate it's failing like Data Services and Schedules.

      Introduce failing state for the listeners.

      Acceptance criteria:

      • the listener gets into failing state if the listener fails to initialize (JMS) or the last check of the listener fails or triggered job fails
      • failing state is visualized in a same way like the failing state of Schedules and Data Services

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              slamam Martin Slama
              Reporter:
              slamam Martin Slama
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: