EUM Action Event failed to parse
There are warning messages that we see in the log which are related to OEM. It seems like it did not parse UEM action event data.
2014-07-28 13:36:09 WARNING [EndUserActionEventRecord] Failed to parse action event
Any idea how to troubleshoot what cause this issue ?
Hi,
we saw this sometimes, when the dynaTraceMonitor beacon request was truncated, because it exceeded limits on app or web server. Most of the time caused by the third party detection sending too much data.
Which dynaTrace Version do you use?
Could you provide whole log file?
regards,
Clemens
As assumed, the action event got truncated because it contained tons of repetitive JS errors and exceeded a length limit.
We fixed an issue in a 5.6 FixPack and in 6.0, where the number of sent JS errors is limited, which will prevent too ling beacons.
Either upgrade to 6.0 or contact support for getting the according 5.6 FixPack (refer to issue JLT-93246).
regards,
Clemens
Thanks for the update.
The fix is to handle exception gracefully by limiting OEM user action data or errors that sent to dynatrace server. Is this correct ?
I'm just trying to asses the impact to this issue.Currently we are droping UEM data which has huge and exceeded limit and it is same case for after fxi also. Please confirm.
Exactly. The fix limits data data sent via the dynaTraceMonitor.
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
