This update enhances the clear() method to include additional Redis keys, ensuring that the horizon:clear-metrics command comprehensively removes all relevant metrics stored in the cache.
Dashboard State Comparison
Before Executing horizon:clear-metrics:
After Executing horizon:clear-metrics (Current Version):
After Updating the clear() Method:
Note on Job Hashes in Cache
Currently, job hashes remain in the cache, as illustrated below. Ideally, these should also be cleared. However, removing them without flushing the entire Redis queue connection or using wildcard patterns ('*') is not feasible unless the specific keys to target are known.
A potential improvement would be to store job hashes under a specific key, such as jobs, to facilitate direct targeting.
This update enhances the
clear()
method to include additional Redis keys, ensuring that thehorizon:clear-metrics
command comprehensively removes all relevant metrics stored in the cache.Dashboard State Comparison
Before Executing
horizon:clear-metrics
:After Executing
horizon:clear-metrics
(Current Version):After Updating the
clear()
Method:Note on Job Hashes in Cache
Currently,
job hashes
remain in the cache, as illustrated below. Ideally, these should also be cleared. However, removing them without flushing the entire Redis queue connection or using wildcard patterns('*')
is not feasible unless the specific keys to target are known.A potential improvement would be to store job hashes under a specific key, such as
jobs
, to facilitate direct targeting.