Operations Basics / Version 2310
Table Of ContentsOn some CoreMedia applications, other caches are employed in addition to the CoreMedia cache.
For example, you can request the current cache size for cache richtext
on a Headless Server with
http://localhost:8081/actuator/metrics/cache.size?tag=name:richtext
The response will then provide the value for the cache size:
{ "name": "cache.size", "description": "The number of entries in this cache. This may be an approximation, depending on the type of cache.", "baseUnit": null, "measurements": [{ "statistic": "VALUE", "value": 91.0 }], "availableTags": [ { "tag": "name", "values": [ "richtext" ] }, { "tag": "cacheManager", "values": [ "cacheManager" ] } ] }
Depending on the application, different cache names
are available. The list of all caches, if any are present,
can be retrieved with a call to
http://localhost:8081/actuator/metrics/cache.size
If no other caches are present for the CoreMedia application, the request will return code 404.
The following table lists available metrics for other caches which are present on some CoreMedia applications. Some metrics support additional tags to further drill down into measurements.
Meter Name | Tags | Description |
---|---|---|
cache.size | The number of entries in this cache. | |
cache.gets | result:hit | The number of cache hits, which are cache lookups that returned a cached value. |
cache.gets | result:miss | The number of cache misses, which are cache lookups that had to evaluate a value. |
cache.puts | The number of values inserted into the cache, after successful evaluation or injection. | |
cache.evictions | The number of values evicted from the cache. |
Table 4.12. Other Cache Metrics