The server side service monitoring -> request attributes is where you can capture data like this but if you're specifically asking about capturing all such attributes I don't believe this is possible. I just tried messing with it and it specifically alerts you that wildcards cannot be used if you try to create such a rule. Consider an rfe if you think this might be a useful feature though the alert makes me think there are good reasons for preventing such "capture all" rules.
To add to the info James provided, please take a look at the blog posts on how to configure request attributes in Dynatrace
Web requests: https://www.dynatrace.com/blog/request-attributes-...
Hope This Helps
If you go into details/purepath/purepath the summary tab acts as the same as right clicking on a purepath node and selecting details. Showing request header information. But I don't think it makes visible anything else as you could in appmon servlet sensor properties using the wild card for Request Attribute, Request parameter etc. This is unfortunate as we would only use the wild card briefly so we could see what was being passed so we can help the app owner who often did not know. Then we could apply that information to make visible only that which was chosen by the app owner. We would immediately turn the wild card off at that point.
This doesn't help at all. I have 100s of attributes that I have been capturing with APM using the wildcard feature, when needed I can then add the specific attributes and remove the wildcard. Most of the time I can leave the wildcard in. It will take me months to find and add all the attributes one at a time. Someone needs to fix this. THIS IS A LOOK FOR ANOTHER PRODUCT LEVEL ISSUE.
Where do we register our displeasure with this decision?