Add HealthMonitoring requirements#3089
Conversation
github-project-automation
Bot
added this to
S-CORE Roadmap and TLC - Technical Lead Circle
|
The created documentation from the pull request is available at: docu-html |
| :security: NO | ||
| :safety: ASIL_B | ||
| :derived_from: stkh_req__functional_req__file_based[version==1] | ||
| :status: invalid |
There was a problem hiding this comment.
Just followed how others are done, we may move it to the correct state in this PR. @aschemmel-tech ?
| The :term:`Health Monitor` shall support deadline supervision to allow | ||
| monitoring timely execution within application to detect timing violations. |
There was a problem hiding this comment.
I think following version reads easier and still provide the same message:
The :term:Health Monitor shall provide deadline supervision to detect timing violations during application execution.
| The :term:`Health Monitor` shall support logical supervision to allow | ||
| monitoring execution flow within application to detect logical errors. |
There was a problem hiding this comment.
I would propose this version:
The :term:Health Monitor shall provide logical supervision to detect logical errors during application execution.
It should read easier without going too much into the details.
| The :term:`Health Monitor` shall support checkpoint supervision to allow | ||
| monitoring periodic execution within application to detect failures. |
There was a problem hiding this comment.
I think you meant alive supervision here. I would propose to reword as follow:
The :term:Health Monitor shall provide alive supervision to detect deviations from the expected execution of application activities.
Please note that I'm not fully happy with deviations from the expected execution of application activities wording, but it follows two other proposals. Feel free to propose alternative wording that doesn't go into too much details (as this is a high level requirement).
If this proposal is accepted, then ID would need to change as well.
| The :term:`Health Monitor` shall provide modular configuration file support to | ||
| configure health checks. |
There was a problem hiding this comment.
I'm not sure what is meant by this requirement...
Do you mean split-able configuration? By this I mean, a single application should be able to have alive configuration in one file and deadline + logical configuration in another file?
Or do we mean that part of configuration can came from C++ code and another part from a file?
Or maybe that we should simply be able to read config from a file?
3 participants
Resolves: eclipse-score/lifecycle#319