Monitor service dependencies with Amazon CloudWatch Application Signals SLOs

[Amazon CloudWatch Application Signals](https://aws.amazon.com/cloudwatch/features/application-monitoring/) now supports creating [Service Level Objectives (SLOs)](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-ServiceLevelObjectives.html) using metrics from your service dependencies. You can now monitor the performance of your services' dependencies, and proactively resolve problems through SLO goal setting, thanks to this new ability. Using Application Signals you can create period-based or request-based SLOs that track key metrics like latency and faults for the outgoing requests from your services to their dependencies. You can see how your dependencies perform and how this impacts the reliability of your overall service. For example, if your e-commerce service relies on a payment processor, you can set an SLO to monitor latency of requests from your createOrder operation to the payment processor. If this SLO degrades, you can quickly investigate the dependency as the potential root cause before it affects your customer-facing service. SLOs on dependencies are available in [all commercial AWS Regions](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Monitoring-Sections.html) where CloudWatch Application Signals is available. Customers can now sign up for the new bundled pricing plan for Application Signals. To learn more, see [Amazon CloudWatch pricing](https://aws.amazon.com/cloudwatch/pricing/).