Dynatrace losing request parameters after enabling bizevents

[phmonte]

After enabling the request body using any json key or even * according to the documentation, the APIs stop responding, the parameters do not reach the API.

The error only happens when using Request Body, any other parameter works correctly.

Message after enable capture request body:

A non-empty request body is required.

Stack:
Azure Web Apps with OneAgent Version: 1.269.166.20230715-203547

Dotnet 6.0

Dynatrace Biz Events

[cesarsaravia]

Hi @phmonte,
I recommend you that if you find an impediment in the configuration of bizevent for .NET, use the Support portal. The agents will help you with more detail, for example asking for images, logs, and any other file that helps to identify and reproduce your problem. Here, the community will help too, but could be answered in hours or maybe days.
https://dt-url.net/lb626l9 

[cesarsaravia]

Hi @phmonte,
What happens when you enable the configuration of bizevent?
Your application is not working? Do the captured events contain empty values on the request body variable?
Could you share with us a screenshot of the error you refer to?

[phmonte]

Thanks for responding @cesarsaravia 

The oneagent log file does not save any error or action information other than conventionally.

I made a drawing to show what is happening.

Remembering that the error only happens with the Request Body, the other options are working correctly.

[cesarsaravia]

Hi @phmonte 
Did you enable the feature flag of capturing .net bizevents? If yes, do you restarted the Asep.Net application?

[phmonte]

Yes, it is enabled and I tried restarting it again.
I tested with other apps (another OneAgent/Webapp) and I have the same problem.

[dannemca]

@phmontedid you got any update on this?

I am suspecting I am facing the same issue.

[phmonte]

So far, no updates @dannemca 

[phmonte]

The problem is not resolved, but an alternative is to disable Webserver Business Events [Opt-In].
A ticket was opened, as soon as it was updated by the dynatrace team, I updated it here with the response.

@dannemca 

[StrangerThing]

I'm also having this problem and have been working with support to resolve. Can update this thread if/when we get to a resolution.

[pmurray30]

I suspect I've just come across this problem with .Net as well. Has anyone had an update?

Also, does this problem only occur with .Net, or have people experienced this with other technologies, such as JAVA?

[dannemca]

.Net here too..

Technologies: .NET (.NET Core 3.1.32.0), ADO.NET (System.Data.Common 4.700.22.56512), ASP.NET Core (3.100.3222.56610), IIS App Pool (10.0.1776 .NET (.NET Core 3.1.32.0), ADO.NET (System.Data.Common 4.700.22.56512), ASP.NET Core (3.100.3222.56610), IIS App Pool (10.0.17763.1), MSSQL Client (4.700.20.6702)
Service technology types: ASP.NET CORE, IIS, IIS app pool, DotNet

[phmonte]

Just to update everyone, the dynatrace team activated some debug logs and sent the files for analysis, as soon as they respond, I will update you,

For now I'm with the paleative solution.

[StrangerThing]

I've been told that a fix for this is in the upcoming OneAgent release of version 1.281, expected end of December.

[dannemca]

I got the same reply on my ticket... in release notes, there is no direct mention for this fix:

https://docs.dynatrace.com/docs/whats-new/release-notes/oneagent/sprint-281

and no ETA so far.

[phmonte]

@dannemca 

I believe it would be this item:

.NET
The request body is no longer stripped away when a Business Event rule to capture the request body is set. (OA-25428)

I haven't tested it yet, as soon as I test it I'll let you know if it worked.

[dannemca]

Yep, they did update the release notes last week. My env is still in 1.279 (OA), when ready, I will test it too.

[dannemca · Accepted solution]

Just upated to 1.281 and issue is solved. Capturing anything with no 400 error anymore.

Note, the OneAgent should be updated in host and also in the process, so a restart is needed.