Better fields not recorded when 'Cache pages for anonymous users' enabled

Thanks for the note. It's true that cached page requests won't have certain types of extra data decorated on them (including node ID). Currently, this has much to do with the state of Drupal when it serves a cached page--specifically, Drupal is only bootstrapped enough to know how to load something from cache and serve it; it knows nothing about nodes or entities or what nodes are on the current page, if any.

On one hand, this is "accurate" or "pure." If you think of the node_id on a given transaction as indication that "a node was loaded in full page view mode on this transaction," then it makes sense that it isn't on cached page transactions. On the other hand, I recognize that it's intuitive to think that you can see how popular a given node is based on the number of transactions decorated with a node_id.

I think the former interpretation / use-case is probably better in the long-run. For instance, if you have a reverse proxy cache in front of your Drupal site, then you won't even see the transaction in Drupal / New Relic (because the request was served from something like Varnish).

Perhaps some better documentation around how to use / analyze the data would help?