Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No way to monitor cache error rates #70

Closed
kpdecker opened this issue Aug 15, 2014 · 2 comments
Closed

No way to monitor cache error rates #70

kpdecker opened this issue Aug 15, 2014 · 2 comments
Assignees
Labels
Milestone

Comments

@kpdecker
Copy link
Contributor

@kpdecker kpdecker commented Aug 15, 2014

When using getOrGenerate, there is no way to monitor cache error rates, performance, etc as the set call's handler is eventually pushed to Hoek.ignore.

There should be some way of exposing catbox errors at any point in the system and ideally there would be generic ops-level tracking so things like the delay for set calls, etc can be tracked upstream.

@hueniverse hueniverse added the request label Aug 16, 2014
@nvcexploder

This comment has been minimized.

Copy link
Contributor

@nvcexploder nvcexploder commented Aug 26, 2014

@kpdecker maybe we can start by adding some emitted events.

@nvcexploder nvcexploder self-assigned this Sep 2, 2014
jagoda added a commit to jagoda/catbox that referenced this issue Aug 4, 2015
This change causes policy objects to emit monitoring events for
all cache operations. All events include the id, time, and error
(if one occured) associated with the operation.

Resolves hapijs#70.
@hueniverse hueniverse assigned hueniverse and unassigned nvcexploder Aug 9, 2015
@hueniverse hueniverse added this to the 4.3.1 milestone Aug 9, 2015
@hueniverse

This comment has been minimized.

Copy link
Member

@hueniverse hueniverse commented Aug 9, 2015

Errors are now surfaced to the callback via #136.

@hueniverse hueniverse closed this in 05f8d60 Aug 9, 2015
@Marsup Marsup added feature and removed request labels Sep 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.