AWS CloudFront Monitoring Update

AWS CloudFront Monitoring Update: AWS released an early & small Christmas Gift to their CloudFront Customers. CloudFront now supports eight more metrics to monitor content distribution. These include:

Cache Hit Rate via HTTP POST and PUT requests, via the percentage of all cacheable requests for which CloudFront served the content from its cache, including errors not considered cacheable requests.

Origin Latency as a quota and the total time spent for requests that are served from the origin, not the CloudFront cache. Origin Latency allows to monitor the performance of your origin server.

Error Rate by status code as a percentage of requests for which the response’s HTTP status code is in the 4/5xx range, in particular 401, 403, 404, 502, 503, and 504.

AWS CloudFront Monitoring Update via AWS Blog.

The possibility to understand: SaaS Product Metrics

Colorful Rulers to Measure
Do you measure up?

Part of the compelling nature of SaaS Products is the possibility to understand the user and improve on the go. Any Product Manager will literally have to understand what are the use-cases for customers and how to focus on the important areas. Just recently our team led the debate which metrics would be the right ones to focus on.

Nancy Wang, Head of Product Management at Amazon Web Services, highlights six product metrics enterprise SaaS companies should track.

In this Article, Nancy Wang, head of Product Management at the most successful cloud service providers, shares her insights on important metrics to keep an eye on. The possibility to understand often goes overboard and requires focus.

The case under discussion in the article revolves around paid products. Derived metrics are a foundation that serves as a blueprint to other products in the SaaS space. Goals differ, but ultimately, to make a product successful, it requires an understanding of how successful customers were, using the product. Following the established funnel pattern, users are being segmented into funnel. Along that funnel, the metrics acquired need to reflect the stage of the journey the user is on.

At the top of the funnel, most often the interaction is anonymous and requires profiling to understand the audience coming in. Further down in the funnel, metrics capture engagement and transaction. Towards the end of the funnel, the metric needs to relate to retention.

Source: Do You Measure Up? Metrics for Enterprise SaaS Product Managers