Can we get future guidance about how to measure the data download size for an ASM monitor? Possible contributors are the size of the script, the size of the JMeter and RBM result structures, and possibly settings that cause the download size to vary (however ASM measures it). Which of these factors are measured in the "data downloaded per month" allowance?
Additionally, are there features in a JMeter or Real-Browser monitor that require more data download size than others?
This is a huge point of confusion for customers. Currently, they receive ASM error messages in their Monitor logs as the only indication that they exceeded their monthly data allowance for a monitor.
What are the steps they can take to measure their monitor data requirements so they can plan their synthetic monitor coverage?
Thanks!