Uploaded image for project: 'Kuali Rice Roadmap'
  1. Kuali Rice Roadmap
  2. KRRM-126

Implement a GUI for business activity monitoring (traffic flow, endpoint availability, metrics, etc.).

    Details

    • Type: Rice Enhancement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Component/s: KSB
    • Labels:
      None
    • Rice Theme:
      Usability
    • Priority Score:
      0
    • Impact if not Implemented:
      Hide
      Without these general, infrastructure monitoring tools being delivered with Rice, functional users will depend on technical resources for commonly needed statistics and views into how the system is working and performing. Institutions that need this sort of data will need to create their own, custom applications to do this sort of reporting. Without being delivered as standard this will be a task that takes away development resources.
      Show
      Without these general, infrastructure monitoring tools being delivered with Rice, functional users will depend on technical resources for commonly needed statistics and views into how the system is working and performing. Institutions that need this sort of data will need to create their own, custom applications to do this sort of reporting. Without being delivered as standard this will be a task that takes away development resources.
    • Priority - KFS:
      No Priority
    • Priority - KC:
      No Priority
    • Priority - KS:
      No Priority
    • Priority - Rice:
      No Priority
    • Effort Estimate:
      Medium ~ 500 hrs

      Description

      This work would involve creating a dashboard for real-time monitoring and altering of Rice functions; primary interest would likely focus on KEW activities. Rice currently offers some of this with the statistics tab, but that if far from comprehensive and could use an overhaul of its user interface. Administration tab > Workflow channel > Statistics link

      This item was broken off from KRRM-51, and it's a bit unclear to me what the full scope would or should be. But for now I will assume it includes the following elements:

      1) Traffic/Message Flow
      2) Endpoint Availability
      3) Metrics related to service bus activity

        Attachments

          Issue Links

            Activity

            Hide
            ewestfal Eric Westfall added a comment - - edited

            Based on the three items listed in the description of the issue, setting effort estimate to "Medium ~ 500 hrs". That might actually be a bit conservative, but i'm not sure exactly how much work it would be for us to be able to start tracking all communication channels over the KSB to be able to produce such a UI.

            Show
            ewestfal Eric Westfall added a comment - - edited Based on the three items listed in the description of the issue, setting effort estimate to "Medium ~ 500 hrs". That might actually be a bit conservative, but i'm not sure exactly how much work it would be for us to be able to start tracking all communication channels over the KSB to be able to produce such a UI.

              People

              • Assignee:
                Unassigned
                Reporter:
                ewestfal Eric Westfall
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: