More detailed Transaction Traces
We have now enhanced Transaction Trace details for both Java and Scala applications.
1. HTTP Response Code
The HTTP Response Status Code is now shown for each trace
2. Request Parameters
Request parameters are now captured for every request and can be seen in the Transaction Traces.
Note: By default capturing request parameters is turned off since some applications may contain sensitive data in the parameters that they don't want to be recorded by us. To enable request parameter capturing, add
captureRequestParams=true to the DripStat config file.
If the transaction being traced resulted in throwing an unhandled exception, that exception will be recorded and shown along with the full stacktrace.
4. Custom Attributes
The DripStat API now allows setting custom attributes for Transactions. These attributes will be visible in the traces.
In your code just call
DripStat.setCurrentTransactionAttributes() with a map of attributes. Eg -
Map<String, String> customAttribs = new HashMap<>(); customAttribs.put("accountId", acconuntId); customAttribs.put("currentUsername", username); DripStat.setCurrentTransactionAttributes(customAttribs);
and you will see the values in the transaction trace:
5. JVM Details
JVM Details is now on a separate tab. It shows you the state of the JVM around the time the trace took place. This helps you narrow down if the root cause was things like increased CPU/GC issues.
How to get all this
- Ensure you are using DripStat Agent 7.2.6 or higher.
- Refresh your browser cache to ensure you see the new Transaction Trace UI.