[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 |
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:
|