Business Events: expected overhead and best practices to limit them

[Fselvanadin]

Hello community,

We are looking for more informations regarding Business events.

We would like to know what kind of impacts we should encounter by collecting request or response payload parameters for all requests processed by a monitored application?

On application side? 

• Application process resource usage? (high CPU/memory usage)
• Application response time overhead?

On OA side?

• Increasing the CPU/Memory used by OA processes? 

Have you any best practices in order to limit these impacts?

Thank your for your help.

Regards

Freddy

[Julius_Loman · Accepted solution]

Basically if you are capturing business events by capturing payload from your application by OneAgent it is accomplished by the code modules. Thus is has impact only on the application process, OneAgent standalone processes are not involved. Mainly on the network traffic (the payload is sent out). Other impact such as memory or CPU is likely not measurable.

I'd more focus on the security view - captured payload may contain very sensitive data and you should carefully design the collection and access control for that.

[Fselvanadin]

Hello Julius,

thank you for your answer.

Because our monitored application is very critical, I think that we are going check its behavior by running load tests w/wo business events configuration.

Thank you also regarding the security side advice.

regards

Freddy

[Julius_Loman]

Sure, that's the best idea. Please share your findings then if possible, but I expect practically zero impact on the application itself. Also, be sure to limit the scope (sometimes it's not easy) of capturing payloads.