Add metrics for MetadataResolvers

Basics

Logistics

Basics

Logistics

Description

Task for adding additional metrics to get at details of metadata resolver configuration. At minimum, includes the type of resolver, information about filters applied, and the remote URI if any. This is tricky with the function-driven resolver used for MDQ since that’s abstracted behind a pluggable function so unsure at this point what’s feasible.

Environment

None

Activity

Scott Cantor

May 23, 2023 at 8:07 PM

Made metricsBaseName general to all resolvers and baked in a better default via the Spring parsers (noted change in release notes).

Added a timer to the reloadable resolvers' refresh method, but confined it to “new” loads. This still breaks a little on pre-expired metadata but that’s more an outlier than the problem of counting “no new metadata” cycles.

Scott Cantor

May 23, 2023 at 5:08 PM

MetadataResolver now exposes a URI and a type, MetadataFilter exposes a type. To avoid classnames ending up in the metrics, I adjusted the Spring parsers to inject a type from the underlying xsi:type we use in the schema, which is clearly part of our API.

The gauge set for the resolvers now exposes the type, URI, and filters installed.

Resize work item view side panel

Done

Details

Assignee

Scott Cantor

Reporter

Scott Cantor

Components

Logging and Metrics

Metadata

Fix versions

5.0.0

Created May 22, 2023 at 5:38 PM

Updated September 13, 2023 at 2:02 PM

Resolved June 1, 2023 at 11:14 PM