Project

General

Profile

Support #23416

Update metric usage in artdaq

Added by Eric Flumerfelt over 1 year ago. Updated 23 days ago.

Status:
Rejected
Priority:
Normal
Assignee:
Eric Flumerfelt
Category:
-
Target version:
-
Start date:
10/14/2019
Due date:
% Done:

0%

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

Description

Since Feature #22342 has been in artdaq_utilities releases for some time, it would probably be a good idea to change the metric instances built into artdaq to use a more diverse set of metric levels, and update the simple_test_configs accordingly.

MetricInventoryWithCategories.xlsx (13.4 KB) MetricInventoryWithCategories.xlsx Updated Metric Inventory Eric Flumerfelt, 10/31/2019 12:46 PM

History

#1 Updated by Eric Flumerfelt over 1 year ago

  • Description updated (diff)

#2 Updated by Eric Flumerfelt over 1 year ago

I have done quite a bit of work, creating a new enum class MetricLevel in MetricData.hh that defines a set of metric level names that can be used to group metrics based on their usage. I have also tried to make it so that the level parameter to both the sendMetric call and in the Metric Plugin configuration are more intuitive and less reliant on hard-coded numbers.

Changes on artdaq-utilities, artdaq, artdaq-demo branch feature/23416_MetricLevelOverhaul.

#3 Updated by Eric Flumerfelt over 1 year ago

  • Assignee set to Eric Flumerfelt
  • Status changed from New to Resolved

#5 Updated by Eric Flumerfelt 23 days ago

  • Status changed from Resolved to Rejected

This change seems unsustainable. I don't have a good idea right now of the best way to manage the metric inventory, but the rise of Grafana-based metric viewers seems to have pretty well obsoleted this approach.

Also available in: Atom PDF