Can we scrape the page and report on some specific values using Dynatrace
Hi,
For some reason none of our methods are returning order value. So i cannot really instrument any method to grab those values. Is there a way to scrape the order confirmation page and report on that value?
Or if we have query, can we turn on bind variable capturing and chart on bind variable values? is it possible that way?
Hi Venkata,
The only measures we can use at the moment for getting the order value are:
- method arguments or return values
- Session entries (including deep object access)
- Web request headers
- Web request parameters
- Cookies (.Net only)
Bind variables are not supported, scraping a page is neither - would be too much overhead if we scrape the whole page and then parse it.
What other customers have done in the past is to include a dummy function in their application where they pass the relevant values as arguments (e.g. username, order value, transaction id) and use a custom sensor to capture them there.
Best, Roman
Hi Roman,
Thx for your reply. few more questions:
Can we capture values from non-primitive data types? i am guessing no. But just want to confirm. For the Order Value, they said we might be able to get them from getter on the data object. But do we see those getter methods when we browse the classess/packages etc? also we don't turn on getter/setters by default right? so is there a way to capture only specific getter by adding a custom sensor rule. Do we need to uncheck the "Ignore getter and setter methods? if so is it going to instrument only the one with custom sensor or is it going to instrument all of them?
Hi,
Non-primitive data types - no, in that case we call the toString method and capture that value. Only exception is getting session values in the servlet sensor, there we do support deep object access. Feel free to add a RFE for this, not the first time I have heard a question like this.
You should see getters like any other method using the class browser and can create a custom sensor rule from there. You hit the problem on the head - by default all getter/setter methods are ignored. This is a global setting that takes higher priority than you custom sensor. Only way around is to turn off the global setting. In that case it will instrument getter/setter methods but only if there is a custom or out-of-the-box sensor rule that matches it. I would try turning it on and then take a look at the Methods dashlet to see if there is a large number of additional method calls being added by this.
Best, Roman
