Task Status
This page is part of the ongoing SWIM communities of interest discussions. The content is working material. It should not be treated as final as it is still subject to review, comment and change.
This page contains discussion on the need for supervision and monitoring of services in a harmonised way.
Problem
We need a mitigation when an information service is down or degraded.
What are the conventions to interface with another application e.g. heartbeat?
Is there a standard way to proceed with supervision.
Previous work
Supervision was addressed in a SESAR project on virtual centres
. This presentation summarises the approach used in the project.
ADS-C Common Service (ACS) may also have something
Are technical standards available for this. Check with SWIM-TEC.
See also Use Case 4 - Service Status Monitoring (see section N3.1.1.4) and also N.3.3.5
Then decide
If we should create a service definition for the service.
Topics
cybersecurity - how does this apply to a supervision service?
will the service have a ticketing mechanism to inform support?
each implementation may have a different set of statuses - is it possible to align them?