Using observability to build trust & improve incident response times
summary
New Relic and Cloudaware integrate with AWS at enterprise scale to turn monitoring into deployable code: Terraform creates cross-account IAM roles, enables CloudWatch pull or Kinesis push telemetry, and provisions agent coverage across ~500 accounts and thousands of EC2s (tests show dashboards at 63,000 compute instances). Alerts use NRQL and carry enriched alert metadata (app ID, category, owner) for routing, prioritization and auto-remediation; status pages and the demoed terraform apply/destroy prove the workflow works and cuts incident response steps.
AI-written summary · about
chapters (30)
- 0:00Introduction and agenda
- 1:28Observability trends
- 3:20Modernizing transformation
- 4:53Partnership for success
- 6:06New York Life case study
- 8:47Observable Enterprise
- 10:05Integration and governance
- 11:47Scaling observability
- 14:04Security and monitoring
- 15:45Centralized data lake
- 17:44Incident communication
- 18:50Service mapping
- 20:53Status page management
- 22:35Actionable alerts
- 24:25Impact assessment
- 26:23Automation and shift left
- 28:24Alerting as code
- 29:48Agent deployment
- 30:55DevOps automation
- 32:37Terraform integration
- 34:15Empowering developers
- 35:14Demo: AWS connection
- 37:00Demo: Self-service
- 38:49Demo: Cost control
- 40:05Demo: Alerting
- 41:57Demo: Query language
- 43:51Demo: Alert modification
- 45:16Push vs Pull monitoring
- 47:28Demo: Service mapping
- 49:24Demo: Cleanup and conclusion
related talks
38mAWS Observability as Code: Leveraging Datadog
01h 01mBetter reliability and uptime with analytics and observability
36mThe road to world-class observability
18mHow AWS Partners use observability to strengthen customer security
13mAchieving Seamless O11y Across Cloud Providers
24mObservability with AWS
20mDesigning the Right Observability Stack in AWS Cloud
13mLightning Talk: Observability-First DevSecOps: Building Resilient Multi-Cloud P...