Prometheus-X
  • πŸ‘‹Welcome to Prometheus-X
  • Overview
    • πŸ’‘What we do
  • Use Cases
    • πŸ”₯Bearers of Fire
      • πŸ‡«πŸ‡·Grande Ecole du NumΓ©rique
      • πŸ‡³πŸ‡΄Sikt
      • πŸ‡«πŸ‡·Ile-de-France Region
      • πŸ‡©πŸ‡ͺAntares
      • πŸ‡«πŸ‡·Institut Mines Telecom
      • πŸ‡«πŸ‡·University of Lille
      • πŸ‡«πŸ‡·Edunao
      • πŸ‡«πŸ‡·Brest Business School
      • πŸ‡«πŸ‡·Cabrilog
      • πŸ‡«πŸ‡·Ecole Centrale Electronique
    • 🀹Skills
      • 🎯Personalised skills matching
      • πŸ“ˆSkills analytics dashboards
    • 🏹Learning traces
      • πŸ‘¨β€πŸŽ“Learning analytics to personalize education
    • πŸ“‘Datasets
    • β˜‘οΈImpact study
  • Building Blocks
    • πŸ“‡Catalog
    • πŸ‘Consent
    • 🀝Contract
    • πŸ†”Identity
    • πŸ”ŽTraceability
    • 🚨Monitoring
    • πŸ‘€Anonymization / Pseudonymization
    • πŸ”ŒInteroperability
      • πŸ—ƒοΈLearning records
      • 🀹Skills data
      • β˜‘οΈImpact study
      • βš™οΈUniversal plugin SDK
      • πŸͺ„AI metadata enrichment
    • 🧠Decentralized AI
      • Decentralized AI training
      • Decentralized AI processing
    • πŸ‘¨β€πŸš€Consent agent
    • βš–οΈTrustworthy AI assessment
    • πŸ“ŠData value chain tracker
    • πŸ”­Distributed data visualisation
    • πŸ‘ŒData veracity assurance
  • Fundamentals
    • πŸš€Vision
    • πŸ“Architecture
    • πŸ—³οΈGovernance
    • πŸ’ΆBusiness model
    • πŸ› οΈWorking Groups
    • πŸ‘‹Join us
    • ⚑Events & Workshops
      • Market-X Workshop
      • πŸ‡ͺπŸ‡ΊOpen letter
  • Extras
    • FAQ
    • Contact
    • Privacy
    • Legals
    • Disclaimer
Powered by GitBook
On this page
  • In short
  • Timeline
  • Objectives and Expected Outcomes
  • Scope
  • Deliverables
  1. Building Blocks

Monitoring

Governance: Monitoring

PreviousTraceabilityNextAnonymization / Pseudonymization

Last updated 2 years ago

In short

  • The monitoring service of Prometheus-X will ensure trust in the infrastructure by allowing to detect and alert on any suspicious use of the data sharing infrastructure

Timeline

Start date: T0 + 0 months (T0 = expected: Q1 2023)

End date : T0 + 4 months

Duration (in months): 4

Where we are now

  • The work will start Q1 of 2023, want to learn more and join the effort: join the !

Objectives and Expected Outcomes

Prometheus services are equipped with a system for monitoring the use of the infrastructure and compliance with legal rules, including consent and contract.

Taking into account data from the catalog, contracts and consents as well as usage data and logs from the PROMETHEUS APIs, in order to be able to detect and alert if a service is bypassing the rules (too few or too many requests depending on what is declared).

The system will alert PROMETHEUS governance and any other legitimate party of a possible infrastructure bypass so that appropriate action can be taken.

The task will implement a dashboard (web/API) of aggregate usage of the platform services.

Scope

  • Implementation of DevOps best practices

  • Deployment of monitoring tools in conjunction with the working groups concerned

  • Development of the dashboard and alert system

Deliverables

#

Availability

Deliverable

1.6.1

T0+2

Unified CI/CD Pipeline

1.6.2

T0+2

Development of the monitoring system architecture

1.6.3

T0+6

Integration with relevant departments (consent, contracting, catalog)

1.6.4

T0+3

Dashboard with performance indicators

🚨
Working Groups