Support of complex service status calculation and propagation rules

XMLWordPrintable

    • Type: New Feature Request
    • Resolution: Fixed
    • Priority: Trivial
    • 6.0.0alpha2, 6.0 (plan)
    • Affects Version/s: None
    • Component/s: Server (S)
    • None
    • Sprint 78 (Jul 2021), Sprint 79 (Aug 2021), Sprint 80 (Sep 2021), Sprint 81 (Oct 2021)
    • 7

      Current implementation of services was designed long time ago, it is rather limited and has significant limitations. Major limitations are:

      • scalability: it does not scale well, also bad user experience when number of services exceeds few hundreds
      • hard to configure: mapping based on triggers does not work well and requires significant effort
      • very limited visualization: no graphical representation of services, no good reporting
      • limited SLA calculation rules
      • no alerting in case of service status changes
      • user permissions: all or nothing

      Proposed functionality will introduce more flexible status calculation and propagation rules.

            Assignee:
            Andris Zeila
            Reporter:
            Rostislav Palivoda (Inactive)
            Team A
            Votes:
            1 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: