Skip to content

Encapsulate supplier, monitor and metric naming logic in some common TestMetric type  #19397

@kennknowles

Description

@kennknowles

After an offline discussion together with @mwalenia we decided to create concrete classes for each metric type (Item_count, byte_count, time). Each class like this will contain:

  • metric name
  • supplier for the metric
  • monitor for the metric

It turns out that all this (along with the monitor/supplier can be encapsulated and then attached to the pipeline/metrics reading where needed. This will also encapsulate the naming logic (so that there are no typos again).

Imported from Jira BEAM-7245. Original Jira may contain additional context.
Reported by: ŁukaszG.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions