Decision Proposal 240, ADR metrics

See also:

• DSB video channel, DP240 Executive Summary

Decision Proposal 240 (DP240) discusses whether Accredited Data Recipients should collect metrics on Data Holder performance, and what form those metrics should take.

Currently Data Holders, or DHs, are required to provide metrics on their own performance.

Should Accredited Data Recipients, or ADRs, collect metrics on DH performance?

If this is presented as an ADR hosted Get Metrics API, what form should it take?

The metrics collected by ADRs should include:

• average response time
• number of invocations
• rejections due to exceeded traffic thresholds
• error responses
• non-conformant response payloads

The ADR Get Metrics API could also include other data.

Should providing the ADR Get Metrics API be mandatory or optional?

Should ADRs be required to provide the Get Metrics API on request from the ACCC?

The DSB invites comment on the following recommendations.

• The DSB defines an ADR Get Metrics API. See DP240 for details.
• Before this API is implemented, ADRs may voluntarily report issues with specific DHs to the ACCC. Reported metrics should be in the form defined for the ADR Get Metrics API.
• Metrics data is categorised by DH brand, with the dataHolderBrandId used in the CDR Register.
• Security endpoint metrics are not included in the ADR Get Metrics API.
• Metrics are returned by the ADR Get Metrics API for the previous full calendar month.

If you have an interest in these questions and topics, read DP240 for more recommendations and additional detail.

To provide your input in response to these questions, add your comments to DP240.

See:

• Decision Proposal 240