You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue should track the missing features of this plugin which could technically be implemented:
Insights - Requests
Cake's HTTP client could rather easily be hooked up to the this feature since events have been added to CakePHP 5.1
Insights - Assets
If assets are served via the AssetMiddleware they could be tracked via the Assets feature of sentry since they are not statically served via the webserver directly.
As far as I can tell there is no event or hook present to easily trace each cache set/get call. The DebugKit can only show how many hits/fails a specific cache pool got but thats not granular enough for what the sentry API requires
Insights - Queues
This should work indipendently on which queue plugin someone uses (either cakephp/queue or e.g. dereuromark/cakephp-queue)
Looking at the docs this is primarily something that needs to be implemented in the worker/runner side of the queue library, not in here.
This issue should track the missing features of this plugin which could technically be implemented:
Insights - Requests
Cake's HTTP client could rather easily be hooked up to the this feature since events have been added to CakePHP 5.1
Insights - Assets
If assets are served via the AssetMiddleware they could be tracked via the Assets feature of sentry since they are not statically served via the webserver directly.
There is just no event or hook to currently trigger such logic
Insights - Caches
As far as I can tell there is no event or hook present to easily trace each cache set/get call. The DebugKit can only show how many hits/fails a specific cache pool got but thats not granular enough for what the sentry API requires
Insights - Queues
This should work indipendently on which queue plugin someone uses (either cakephp/queue or e.g. dereuromark/cakephp-queue)
Looking at the docs this is primarily something that needs to be implemented in the worker/runner side of the queue library, not in here.
Cron
See #11
The text was updated successfully, but these errors were encountered: