Project

General

Profile

Feature #5984

Implement the "report" functionality infrastructure

Added by Kurt Biery over 5 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Additional Functionality
Target version:
-
Start date:
04/21/2014
Due date:
% Done:

0%

Estimated time:
80.00 h
Experiment:
Co-Assignees:
Duration:

Description

DAQ processes within that artdaq system currently support a "report" operation. The purpose of this operation is to allow external entities to gather information about the internal status and performance of the processes. This operations takes a string "which" argument that is intended to allow users to specify the particular information that they are interested in.

Only a limited use of this functionality has been made so far. The Aggregator supports queries of a handful of quantities such as number of events and file size.

The original design of this functionality included a general-purpose Report object that classes could use to report their information and a model of using different engines to transform the Reports into serialized data that would be returned to the caller.

The purpose of this Issue is to revisit and finalize the design of the infrastructure that is needed to support this functionality and implemented the selected design in the code.

IMAG0060.jpg (763 KB) IMAG0060.jpg whiteboard picture of Report-related class diagram Kurt Biery, 04/21/2014 02:49 PM

Related issues

Related to ds50daq - Feature #4032: Add DAQ monitoring to the ds50daq systemClosed06/07/2013

History

#1 Updated by Kurt Biery over 5 years ago

#2 Updated by Eric Flumerfelt almost 3 years ago

  • Category set to Additional Functionality
  • Target version deleted (577)


Also available in: Atom PDF