BPO Report - Cache Hit Ratio Calculation

[#1]

Request for Feature Enhancement (RFE) Summary:	Would like the following feature - Cache Hit Ratio to be refined as a factor for Optimization in BPO Reports
Use-case:	We received a BPO Report highlighting Cache Hit Ratio of 80% against Adobe's recommendation of 90%. The implementation is AEMaaCS thus using Adobe's Fastly CDN. The metric is also calculated at CDN end. However, a large number of requests which are received at Dispatcher are not cache able. (Health Check based requests like /system/probes/health, /system/probes/live, /system/probes/ready and Bot Based Requests like GET /3x.php/?3x=3x which are blocked at Dispatcher)
Current/Experienced Behavior:	The metric calculated at CDN would take into account both bot based requests which are blocked at Dispatcher (but not CDN!) and Health Check based requests which are not cached and served to Publish instances via Dispatcher.
Improved/Expected Behavior:	The metric should exclude these service based requests (if not already done). Also, these bot requests should ideally be excluded from the data collected at CDN. (This might be possible only if these requests are blocked at CDN.)
Environment Details (AEM version/service pack, any other specifics if applicable):	AEMaaCS - Version - 2023.1
Customer-name/Organization name:	TA Digital
Screenshot (if applicable):	These logs are manually analyzed for 16th March 2023.
Code package (if applicable):

@kautuk_sahni, @Jagpreet_Singh_ 

[#2]

@Rohan_Garg 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-12886. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.