📄️ Introduction
Monitoring is the key service needed to gain insights into an infrastructure. It needs to be continuous and on-demand to quickly detect, correlate, and analyse data for a fast reaction to anomalous behaviour. The challenge of this type of monitoring is how to quickly identify and correlate problems before they affect end-users and ultimately the productivity of the organisation. Management teams can monitor the availability and reliability of the services from a high level view down to individual system metrics and monitor the conformance of multiple SLAs. The key functional requirements are:
📄️ Use Case 1: Monitor an Onboarded Service (central one)
Introduction
📄️ Use Case 2: Monitor an Infrastructure (community)
Introduction
📄️ Use Case 3: Integrate External Monitoring service
Introduction
📄️ Use Case 4: Combine Results of existing ARGO Tenants.
Introduction
📄️ Use Case 5: Third-party services exploiting EOSC Monitoring data
Introduction
📄️ Get Monitoring A/R Data based on the Resource-ID
Introduction
📄️ Get Monitoring Status Data based on the Resource-ID
Introduction
📄️ Process events/alerts directly from the source(AMS)
All the events that compromise the produced alerts of the monitored