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

Operations Dashboard in cluster

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: rel-5-8-0
    • Component/s: None
    • Security Level: Users (General product issues)
    • Story Points:
      5
    • QA Testing:
      UNDECIDED
    • Sprint:
      Blue Sprint 107, Blue Sprint 108

      Description

      The Operations Dashboard should work in Cluster:

      • same dashboard on all nodes (i.e. same view on each node where I can login)
      • information used by Monitors are calculated based on state of the whole cluster (e.g. listener failing on any node can influence a Monitor state)
      • changes to the dashboard are propagated to the whole cluster (e.g. I add a monitor on node1, then soon users on node2 will also see it)
      • dashboard API works on all nodes and provides a cluster-wide view
      • if 2 entities change state on 2 nodes at the same time, monitor that uses it works correctly
        • example - on 1 node schedule fails, on 2nd node listener fails, then the one monitor that uses them will have correct resulting state

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              salamonp Pavel Salamon
              Reporter:
              urbanj Jaroslav Urban
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: