topic Re: Capture Size Limit of BizEvent in Open Q&A

Capture Size Limit of BizEvent

r_weber — Thu, 28 Nov 2024 18:24:03 GMT

Can anyone provide what the capture limits (oneagent) of business events are on the payload (request/response) are?

I have a situation where, although requests itself are captured and details are extracted from headers, the response payload (JSON) and the captured data fields that depend on it are empty. The current assumption is that (since the response can't be null) that a limit kicks in and the payload is ignored if it exceeds a certain size? (Which makes sense performance -wise, but it would be good to know)

Re: Capture Size Limit of BizEvent

p_devulapalli — Fri, 29 Nov 2024 07:22:55 GMT

@r_weber , looks like its 5 MB per request when ingesting via API, not sure if same applies for OneAgent?

https://docs.dynatrace.com/docs/shortlink/ba-api-ingest#payload-formats

Re: Capture Size Limit of BizEvent

r_weber — Mon, 02 Dec 2024 15:44:34 GMT

It must be much less than that..more in the few kilobytes range.

Re: Capture Size Limit of BizEvent

PacoPorro — Mon, 02 Dec 2024 15:53:39 GMT

According with this information

Deep payload inspection extracts up to 64KB of business data from in-flight application requests and responses

https://www.dynatrace.com/news/blog/the-value-of-business-events-how-it-can-increase-business-agility/

Re: Capture Size Limit of BizEvent

r_weber — Mon, 02 Dec 2024 16:32:35 GMT

Confirmed the limits with support:

OneAgent limits:
• Max req/res body payload size 64132 bytes (~64 KiB)
• Period length 1000 (1 second)
• Max events in a period 200
• Max payload in a period (1 MiB)

Re: Capture Size Limit of BizEvent

Jesus_igl — Wed, 22 Jan 2025 12:22:12 GMT

Hi, Does anyone know what happens if the body exceeds 64Kb? does it keep the first 64Kb or does it not pick up the record and leave the data empty?

Thanks

Re: Capture Size Limit of BizEvent

r_weber — Wed, 22 Jan 2025 12:45:07 GMT

The body is not captured, or it cannot be safely interpreted (e.g. a truncated JSON payload would not be parsed or any fields extracted) - you would get a null value.
I asked support to extend our capture limit and they increased it to 128Kb (works fine for us now)