Project

General

Profile

Idea #22355

Add "Minimum" and "Maximum" to MetricMode, make it a flags enum

Added by Eric Flumerfelt 5 months ago. Updated about 2 months ago.

Status:
Closed
Priority:
Normal
Category:
artdaq-utilities
Start date:
04/11/2019
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Duration:

Description

For some metrics, such as Shared Memory Available %, it may be desirable to have the minimum or maximum value of the metric during the interval available as a metric.

Thinking slightly more about this, we already have AccumulateAndRate, and one could easily want the AverageAndMinimum, AccumulateAndMaximum, and so on, so it might be best to make the MetricMode field settable via bitwise OR, i.e. MetricMode::Average | MetricMode::Minimum, MetricMode::Accumulate | MetricMode::Maximum, etc.

Thinking even more about this, it may be desirable to revise this functionality completely, such that each MetricPlugin instance can decide which Modes to report to its back-end. Most of the data needed to calculating each mode's value is already available to the MetricPlugin, and it would not be difficult to modify MetricData to ensure that the rest is available as well.


Related issues

Blocks artdaq - Feature #22615: Fragment latency trackingClosed05/21/2019

History

#1 Updated by Eric Flumerfelt 4 months ago

  • Status changed from New to Resolved

Implementation on artdaq-utilities:feature/22355_MetricMode_BitwiseOr.

#2 Updated by Eric Flumerfelt 3 months ago

#3 Updated by Ron Rechenmacher 3 months ago

  • Status changed from Resolved to Reviewed

reviewed

#4 Updated by Eric Flumerfelt about 2 months ago

  • Target version set to artdaq_utilities v1_05_00
  • Assignee set to Eric Flumerfelt
  • Status changed from Reviewed to Closed
  • Category set to artdaq-utilities


Also available in: Atom PDF