EUM Action Event failed to parse

Question

Question by Sathish S. · Jul 29, 2014 at 05:20 AM ·

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 ?

0

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 1 · 2014-07-31T17:17:15Z

Answer by Clemens F. · Jul 31, 2014 at 05:17 PM

Exactly. The fix limits data data sent via the dynaTraceMonitor.

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 2 · 2014-07-31T00:27:40Z

Answer by Sathish S. · Jul 31, 2014 at 12:27 AM

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.

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 3 · 2014-07-30T16:30:48Z

Answer by Clemens F. · Jul 30, 2014 at 04:30 PM

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

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 4 · 2014-07-30T00:16:44Z

Answer by Sathish S. · Jul 30, 2014 at 12:16 AM

oemerror.log

I have attached failed transaction in the entire log.

We are using DT 5.6

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 5 · 2014-07-29T19:40:34Z

Answer by Clemens F. · Jul 29, 2014 at 07:40 PM

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

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

EUM Action Event failed to parse

5 Replies

Join the conversation!

NAM 2019 SP3 is available

LIVE WEBINAR

Follow this Question

Forum Tags