[MGNLRESTCL-48] Monitor health of a REST Client endpoint Created: 14/Feb/19  Updated: 02/Apr/19

Status: Open
Project: REST Client
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Documentation update required:
Yes
Epic Link: Easy Outbound REST
Sprint: Phase 4

 Description   

As a developer or administrator, I want to monitor the endpoints behind a REST client to ensure that they are healthy and not causing problems. 

Relying on external systems for a live website can introduce risk to a project, especially when the external content is accesses by a live "dynamic" connection, and is not simply synched to the local system. There is value in ensuring that the REST client is healthy, and that the response format has not changed.

Acceptance Criteria:

  • Ability to configure a monitor for a REST Client which can run on a schedule.
  • Ability to configure simple tests of the response, to ensure that the format is expected.
  • Ability to configure commands to execute when a monitored system is determined to be offline or unstable - such as send messages.
  • Ability to configure commands to execute when a monitored system response format appears to have changed.

Generated at Mon Feb 12 10:42:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.