search

ConsumerDataStandardsAustralia / standards-maintenance

This repository houses the interactions, consultations and work management to support the maintenance of baselined components of the Consumer Data Right API Standards and Information Security profile.
41 stars 9 forks source link

Metrics: Performance threshold including SDH #605

Closed perlboy closed 8 months ago

perlboy commented 11 months ago

Description

The Get Metrics model PerformanceMetrics specifies a description of "Percentage of calls within the performance thresholds" which effectively captures all calls regardless of Primary or Secondary Data Holder behaviours. The indication in the MI call today was that this wasn't intentional however current implementations are reporting to the Regulator these metrics inclusive of all calls.

Note: I've created this pretty quickly for consideration in this MI and therefore have not had a chance to pass this through Biza.io's Data Standards Committee.

Area Affected

Change Proposed

Alter description of these attributes to be explicitly "calls for which Primary Data Holder is responsible".

CDR-API-Stream commented 10 months ago

This is a reasonable clarification and aligns with the intent of these metrics. The performance metrics are not intended to aggregate the performance of the primary and the secondary data holder into a single number as that would actively undermine the ability to understand the operational performance of both data holders.

We would therefore consider this change a defect or clarification, rather than a material change.

If there are no objections we will include this in the next standards revision as a clarification.

nils-work commented 9 months ago

A fix for this issue has been staged for review: https://github.com/ConsumerDataStandardsAustralia/standards-staging/commit/a7de13e8e775506144e80a30d3bbc205ffa77b5c

plus detail for Metrics v3 and v4: https://github.com/ConsumerDataStandardsAustralia/standards-staging/commit/a24ccf2640407c771439efa1460c5b2d1a0e8556

nils-work commented 8 months ago

This change has been incorporated into version 1.27.0