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

Alerts and notification configuration for Schedules

    XMLWordPrintable

    Details

    • Story Points:
      40
    • QA Testing:
      UNDECIDED
    • Sprint:
      Green Sprint 117, Green Sprint 118, Green Sprint 119, Green Sprint 120, Green Sprint 121, Green Sprint 122

      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 schedule without a need to deep dive and study its tasks history.

      The schedules have failing state which is visualized in Server UI but the condition for switching to failing state is not configurable. The schedule gets red if the last execution fails. This is not sufficient. Example: for often running schedule not every particular failure of executed job is a problem.

      Introduce Alerts and Notifications configuration tab for the Schedules and make the failing state configurable similar to Data Services.

      Acceptance criteria:

      • failing state for the Schedules is configurable and it works in the same way as the configuration in Data Services
      • email notification of failing state is introduced and it work like email notification for Data Services

        Attachments

          Issue Links

          1.
          Change tutorial Sub-task Closed Roland Botka
          2.
          Create new selenium tests for Alert and Notification Sub-task Closed Tomas Hajek
          3.
          Check import and export Sub-task Closed Kamil Koci
          4.
          Add Alerts and Notification tab to Schedules detail Sub-task Closed Roland Botka
          5.
          Change table of Schedules Sub-task Closed Roland Botka
          6.
          Change HealthMonitor Sub-task Closed Lukas Adamek
          7.
          Fix old schedules selenium tests Sub-task Closed Filip Vasko
          8.
          Changes algorithm to work with schedules too Sub-task Closed Lukas Adamek
          9.
          Update permissions Sub-task Closed Roland Botka
          10.
          Update DB schema Sub-task Closed Roland Botka
          11.
          Change DataServiceHealthListener to HealtConfiguration Sub-task Closed Kamil Koci
          12.
          Visualization of error states Sub-task Closed Roland Botka
          13.
          Tabs are not visible in edit mode Sub-task Closed Roland Botka
          14.
          Visualization on menu item Sub-task Closed Martin Slama
          15.
          Update menu item when schedule health state changes Sub-task Closed Roland Botka
          16.
          Data Services are not marked as failing in the UI Sub-task Closed Kamil Koci
          17.
          Failing schedule is not marked as failing after changing the alert settings Sub-task Closed Lukas Adamek
          18.
          DB test Sub-task Closed Martin Slama
          19.
          Could not perform DB schema update: Patch 0140_move_health_configuration.sql failed Sub-task Closed Lukas Adamek
          20.
          Form in the Alerts tab is not validated Sub-task Closed Roland Botka
          21.
          Cannot change "Failure indication" on schedules, data services and listeners Sub-task Closed Lukas Adamek
          22.
          JmsMessageListenerTest.testProcessingOfTextMessageByTheGraphTriggeredByTheJmsListener fails Sub-task Closed Tomas Hajek
          23.
          HealthMonitor ERROR Could not process REST invocation record Sub-task Closed Lukas Adamek
          24.
          Existing schedules have state null Sub-task Closed Roland Botka
          25.
          Many warnings 'Trigger refers to unknown scheduleId' in server test's all.log Sub-task Closed Roland Botka
          26.
          "ERROR Could not process REST invocation record" in Selenium tests Sub-task Closed Lukas Adamek
          27.
          "Couldn't store trigger 'group.trigger_15' for 'group.noOp'" in Selenium tests Sub-task Closed Lukas Adamek
          28.
          Test "ds_custom_success_status_code" failed on cluster Sub-task Closed Lukas Adamek
          29.
          Exception when creating event listener Sub-task Closed Roland Botka
          30.
          Tests HealthStatusTest fail Sub-task Closed Kamil Koci
          31.
          ComponentNotFoundException: Cannot find component for expression "menuForm:scheduleMenuElementId" referenced from "j_id1" Sub-task Closed Roland Botka
          32.
          DataServiceJob - implement getName() Sub-task Closed Roland Botka
          33.
          Create and update documentation Sub-task Closed Martin Predny
          34.
          Update screenshots in documentation Sub-task Closed Kamil Koci
          35.
          "ERROR Could not process REST invocation record" in Server core test log Sub-task Closed Lukas Adamek
          36.
          "ERROR Cannot not mark Data Service job as working" in Server core test log Sub-task Closed Lukas Adamek
          37.
          Rename and create new health monitor config properties Sub-task Closed Roland Botka
          38.
          Error creating bean with name 'smtpCtrl': NullPointerException Sub-task Closed Roland Botka
          39.
          HealthMonitor - add integration tests for DataServices, Schedules, EventListeners Sub-task Closed Lukas Adamek

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: