Content
View differences
Updated by Wieland Lindenthal over 2 years ago
**As** an administrator responsible \- Introduce healthy/unhealthy property for the integration storages.
- It can be a set of OpenProject with columns related to a file storage system, such as Nextcloud which are able to answer at least the following questions:
**I want to** have clear and timely information about - Is the health of storage healthy?
- If not healthy, then since when?
- If not healthy, then what is the setup problem?
- If not healthy, then have admins been notified already?
\- In case of the integration job badly behaviour set the state to be unhealthy and notify admin(s).
**so that** I \- If something goes wrong with the job
- It is an expected issue that admins can take resolve => we mark storage as unhealthy and notify admins with probable causes and steps how to fix it regularly till the ones storage is healthy again.
- It is not an expected issue that aren't working correctly.
Background:
As can or cannot be resolved by admins => we fail the integration connects two independent systems that communicate over job with an exception, mark it as unhealthy and anyway notify admins about the (Inter)net there is a multitude of components involved problem.
\- When an unhealthy storage gets back to make it the connection be successful. It is relatively easy to make healthy?
- When the setup fail.
The consequence of a faulty/buggy integration can be huge storage synchronization passes without unexpected behavior we mark it as whole business workflows can be forced healthy again.
- Do we need to halt. Therefore it is crucial that faulty setups get detected timely. notify admins about cured storages?
Administrators, How to notify admins about ill storages?
- Through email
- Not on every synchronization failure, but also the OpenProject support team need on schedule. For instance: on first transition to unhealthy state and then once per day.
- One possible option is to have better tools at hand to debug faulty integrations. When debugging a bad state of the integration it saves a lot of time if certain reasons can be excluded easily, such as server crashes or network issues. separate cron job which once per day notifies about every unhealthy storages.
This EPIC entails * [ ] Have an admin informed via email about storage getting unhealthy and storage getting back healthy
* [ ] Expose storage health status in OpenProject UI.
**As** a couple of FEATUREs that shall improve admin
**I want to** _to see the analysis of the health status of a file storage integration and reduce Storages_
**so that** _I can take steps to fix the time until a bad setup gets detected. ones that aren't working correctly._
**Acceptance criteria**
* _\[enter acceptance criteria\]_
* _..._
- It can be a set
**I want to** have clear and timely information about
- If not healthy, then since when?
- If not healthy, then what is
- If not healthy, then have admins been notified already?
\- In case
**so that** I
- It is an expected issue that admins
- It is not an expected issue
Background:
As
\- When an unhealthy storage gets back
- When
The consequence of a faulty/buggy integration can be huge
- Do we need
Administrators,
- Through email
- Not on every synchronization failure,
- One possible option is to
This EPIC entails
* [ ] Expose storage health status in OpenProject UI.
**As**
**I want to** _to see
**so that** _I can take steps to fix
**Acceptance criteria**
* _\[enter acceptance criteria\]_
* _..._