The EOSC-hub project has ended. This space is READ ONLY

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Service Description

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 analyze data for a fast reaction to anomalous behavior. 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 organization. The ARGO Monitoring Service (https://argo.egi.eu/egi/documentation) provides a flexible and scalable framework for monitoring status, availability and reliability of a wide range of services provided by infrastructures with medium to high complexity. ARGO generates reports using customer defined profiles (e.g. for SLA management, operations, etc.). During the report generation, ARGO takes into account custom factors such as the importance of a specific service endpoint and scheduled or unscheduled downtimes. Foundations of ARGO Monitoring Service are:

  • Sources of truth - registries containing information about what should be monitored and how the monitoring should be performed.
  • Configuration Management Database is a registry which contains information about the topology of the infrastructure - entities such as sites, service endpoints, entity organization (groups, hierarchies) and contact information of users responsible for operations.
  • Registry of metrics for monitoring different services .

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 dashboard design enables easy access and visualization of data for end-users. APIs are also supported so as to allow third parties to gather monitoring data from the system .

Features

The key features of ARGO Monitoring Engine are:

  • Multiple reports availability and reliability,
  • Multiple Tenants
  • High availability of the different components of the system
  • Loosely coupled: support API’s in the full stack so that components are independent in their development cycles
  • Support for Topology Configurations, Metrics and profiles to add flexibility and ease of customisation.
  • Dashboard design
  • Real Time Alerts
  • Customer Defined thresholds


  • No labels