PERF07-BP02 Analyze metrics when events or incidents occur
In response to (or during) an event or incident, use monitoring dashboards or reports to understand and diagnose the impact. These views provide insight into which portions of the workload are not performing as expected.
When you write critical user stories for your architecture, include performance requirements, such as specifying how quickly each critical story should execute. For these critical stories, implement additional scripted user journeys to ensure that you know how these stories perform against your requirement.
Common anti-patterns:
-
You assume that performance events are one-time issues and only related to anomalies.
-
You only evaluate existing performance metrics when responding to performance events.
Benefits of establishing this best practice: In determine whether your workload is operating at expected levels, you must respond to performance events by gathering additional metric data for analysis. This data is used to understand the impact of the performance event and suggest changes to improve workload performance.
Level of risk exposed if this best practice is not established: High
Implementation guidance
Prioritize experience concerns for critical user stories: When you write critical user stories for your architecture, include performance requirements, such as specifying how quickly each critical story should run. For these critical stories, implement additional scripted user journeys to ensure that you know how the user stories perform against your requirements.
Resources
Related documents:
Related videos:
Related examples:
