Observability

[bluedoors]

Is your feature request related to a problem? Please describe.
The business outcomes list:

Measured - Provide real-time metrics for code quality, speed (deployment frequency and deployment lead time), security (security control automation %, mean time to resolve security errors), and reliability (change failures and time to restore service). View metrics through a real-time dashboard. When instrumentation is not yet possible, create a Likert-based questionnaire to determine these metrics across teams.

Yet the diagrams, and reference implementation leave out observability of the pipeline itself (or indeed set of pipelines when invarably multiple pipelines will exist within an organisation)

Describe the solution you'd like
Would be good to have the reference architecture and refrence implementtaion cover in more detail the measurement aspect, and visualisation of the same

[cplee]

Love this @bluedoors - some metrics (e.g. deploy frequency and lead time) will be very easy to add to the reference implementations. However the others (e.g. time to restore service) are more difficult. Would you see value in delivering these metrics incrementally? Any objections to CloudWatch dashboard for this?