The Scorecards templates library provides a streamlined way to address engineering and business use cases. By using best practices from large enterprises, the library offers solutions for common engineering challenges.
Each template in the library is fully customizable to meet your organization's standards. You can modify queries, rules, and thresholds to tailor the Scorecards to your needs.
Scorecard templates
Purpose: Validates if your services are ready for production deployment by checking defined objectives, alert configurations, and recent deployment activity.
Importance: Ensures minimal downtime and high service quality during deployment.
Prerequisites:
Key rules:
- Defined SLOs: Establishes clear targets for performance and reliability.
- APM service alerts configuration: Ensures alerts are set for prompt issue detection.
- Recent deployments: Verifies successful deployments within the last month.
Purpose: Assesses visibility of team ownership, tagging, code repositories, and documentation.
Prerequisites:
- New Relic Teams
- GitHub integration (if applicable)
Key rules:
- Team ownership: Links services to responsible teams through ownership tags.
- Defined code repos: Checks for associated code repositories.
Purpose: Ensures systems are prepared to handle alert conditions by verifying the availability of runbooks for operational procedures.
Importance: Promotes transparency and aids in incident resolution.
Prerequisites: New Relic alerts
Key rules:
- Team ownership: Links services to responsible teams through ownership tags.
- Defined code repos: Checks for associated code repositories.
Purpose: Evaluates key performance metrics affecting user experience, including loading speed, interactivity, and visual stability.
Importance: Optimizes user experience by ensuring fast load times, responsive interactions, and stable layouts.
Prerequisites: New Relic browser monitoring
Key rules:
- Largest contentful paint (LCP): Measures main content load speed.
- First input delay (FID): Assesses responsiveness to user interactions.
- Cumulative layout shift (CLS): Ensures minimal layout shifts.
Purpose: Assesses reliability against AWS standards, ensuring security and redundancy for cloud operations.
Importance: Secures cloud infrastructures and ensures operational continuity.
Prerequisites: New Relic AWS monitoring
Key rules:
- EFS encrypted check: Confirms encryption of Elastic File System (EFS) volumes.
- RDS instance backup retention: Checks backup retention periods for Relational Database Service (RDS).
- RDS deletion protection: Verifies deletion protection.
- RDS MultiAZ presence: Ensures deployment across multiple availability zones (MultiAZ).
- RDS auto minor version upgrade check: Confirms automatic minor version upgrades.
Purpose: Evaluates resource allocation and process improvements using key performance indicators.
Importance: Quantifies software delivery performance, aiding strategic decision-making.
Prerequisites:
Key rules:
- Deployment frequency: Tracks successful deployment rates.
- Mean time to recovery: Measures recovery time from failures.