Activity Logs events are truncated when exported to EventHub

Jiri Formacek 6

Hello, this is to follow up on question originally asked here: activity-logs-events-are-truncated-when-exported-to-eventhub-amp-storage (forum archived now).

I wanted to ask about status of problem being fixed - we process Azure AD Activity log streamed to Event Hub and struggle with truncating as well. Not only the resulting information is not complete, but also resulting JSON is not valid, which is really bad from parsing and processing perspective.

Thanks for update and possibly ETA for fix (at least avoiding invalid JSON being produced)
Jiri

Swathi Dhanwada 18,806 Reputation points Microsoft Employee

2020-07-16T14:39:03.86+00:00

@Jiri Formacek Thanks for following up on this. AFAIK, there isn't any ETA mentioned as of now. However, I will check with engineering team and provide you an update on the issue.
Swathi Dhanwada 18,806 Reputation points Microsoft Employee

2020-07-28T04:29:57.167+00:00

@JirFormacek Engineering team has planned to work on it in this semester . I will keep you posted with the updates.

Thanks for your patience and understanding.
Eric Latour 6 Reputation points Microsoft Employee

2020-09-21T09:42:14.68+00:00

Hello,
Could you share an update on this ?
Rgd
Michael Olsson 6 Reputation points

2022-04-11T15:45:28.827+00:00

Hi team,

I have found a similar problem using the diagnostics logging feature with Logic Apps, some records written to the EventHub are truncated, initially, I thought this was with the Message string in the error (last entry), However, with additional logging around this problem it happens randomly on the record object as well.

The string is received from the event hub using the latest Azure SDK and is roughly 45-80.000 characters when this happens.

1st example (random place): 1718529512375CU201"},"api":{}}}]}
2nd example (last part of the last record) : ate: 2022-0...}]}
Gintaras 5 Reputation points

2024-03-27T06:20:08.86+00:00

Is there any progress on this? The page linked by OP no longer exists. We are experiencing this issue as well.
Events are being truncated even though they are nowhere near any size limits we could find (our largest events are ~80KB, and the truncated value contains only ~16KB of data).
jeff williams 0 Reputation points

2024-12-29T13:20:53.88+00:00

I'm having the same issue. Very frustrating.

Share via

Activity Logs events are truncated when exported to EventHub

Your answer