Issue Summary

CloneCacheHit and CloneCacheMiss metrics are reported in the Bitbucket Main Java process JMX, but they should be listed under the Mesh Sidecar JMX (8.x or higher).

CloneCacheHit and CloneCacheMiss contains incorrect data (7.21.x or higher)

This is reproducible on Data Center: YES

Steps to Reproduce

1. Clone the same repository multiple times
2. Check the CloneCacheHit and CloneCacheMiss values on Bitbucket Main Process JMX

Expected Results

The CloneCacheHit and CloneCacheMiss metrics shouldn't be listed under the Main bitbucket Process JMX but should be under Mesh Sidecar JMX metrics:type=packCache,name=hits and metrics:type=packCache,name=misses (8.x or higher)

The CloneCacheHit metric should be incremented if there is a cache hit.

Actual Results

1. CloneCacheHit is reported as 0 even when the Clones are cache Hit
2. CloneCacheMiss shows the same value as the CloneRequestCount which is also incorrect

Workaround

For versions 8.x or higher, monitor the JMX of the Mesh Sidecar process to track ticket statistics and SCM cache-related information.

metrics:type=packCache,name=hits

metrics:type=packCache,name=misses