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
Currently our agent is assuming that all Active Support notifications for the Active Support library's own API usage are caching related. For our segment naming and event payload processing, this assumption of caching will not work well for events that are messages related instead of caching related.
From the Rails documentation on notifications, note that Active Support events are grouped into either Caching or Messages. We should either split our Active Support instrumentation into 2 separate groups or make the existing single solution dynamic enough to handle both event groups.
The text was updated successfully, but these errors were encountered:
Currently our agent is assuming that all Active Support notifications for the Active Support library's own API usage are caching related. For our segment naming and event payload processing, this assumption of caching will not work well for events that are messages related instead of caching related.
From the Rails documentation on notifications, note that Active Support events are grouped into either
Caching
orMessages
. We should either split our Active Support instrumentation into 2 separate groups or make the existing single solution dynamic enough to handle both event groups.The text was updated successfully, but these errors were encountered: