...

• Alarm Handling
  • The Fast Monitoring process should output an xml file with a list of the alarms/warnings/errors detected on the produced monitoring histograms
  • This file should be registered with the data catalog (is it there already?)
  • A notification should be added to the Logging application which should point to the Data Quality Monitoring application (is it possible to add the desired target link as part of the notification's metadata?)
  • The file needs to be ingested producing summary and detailed information on the alarms/warnings/errors
• Data Trending
  • Design tables to ingest the trending data: some 20K quantities at a frequency between 10 seconds and 5 minutes
  • We might have several copies of the same tables to accumulate data at different frequencies
  • Given the volume of data a database table only approach might be insufficient. We might have to consider a hybrid solution that involves reading data straight from tuple files (less efficient that reading from a db)
  • Write the code to ingest the data.
  • Find somebody responsible for the ingestion code. Should be somebody that understands the data! (in other words not me)
  • Write the code to produce trends
• Improve the application's UI
  • User preferences
  • Improvements based on user's feedback

Source Monitoring

Scope

Status

To-Do List

Data Processing

Scope

Status

To-Do List

Portal

Scope

Status

To-Do List

Ops Log

Scope

Status

To-Do List

Cross Trending/Reports

Scope

Status

To-Do List