Open fallwith opened 4 months ago
Note that we subscribe to all ActiveSupport notifications, but then only process the caching ones due to this regex: https://github.com/newrelic/newrelic-ruby-agent/blob/4e3175ec784d6f760b33e073b8adb7721b11333b/lib/new_relic/agent/instrumentation/active_support_subscriber.rb#L57
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.