ISISComputingGroup / ISISComputingGroup/IBEX

System & server health check (independent of GUI & nagios)

Open
#3,752 17 comments 0 reactions 0 assignees View on GitHub
Friday
Dominant language
No language data
Stars
6
Forks
2
Avg merge
16h 40m
Merged PRs (30d)
2

Description

As a VESUVIO instrument scientist I want to know if either my block or instrument archiver is not running so that I can take remedial action.

This information in cycle is alerted on by Nagios but the instrument scientist would like to know.

Preferably something similar to the error users see when the block server is not up.

NB Check should be that it is healthy not the process is around.

## Acceptance Criteria
1. Finish defining the acceptance criteria with what we expect
2. Consider the distribution methods
3. Nagios may be enough on it's own

## Notes

Per discussion in comments, this would ideally be a check independent of the GUI, which would then be usable by other components (e.g. potentially the web dashboard, genie_python). We may wish to internally re-use some of the nagios infrastructure, but this should be ultimately scientist-facing which nagios is not.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.