Frequency and volume of tracing

You can use the tracing infrastructure to trace all events and data, but doing so could have a serious impact on the application’s performance. Identifying relevant data becomes difficult if too much data is captured. Not enough data, on the other hand, is too abstract to be helpful and might result in loss of useful information. To balance between these extremes and prioritize the messages, PAH ensures that these activities are accomplished:

• Trace data is verified to be important and useful.
• Additional tracing is enabled in sections with relatively higher levels of functional complexity or business logic.
• Additional tracing is enabled in sections where the application interacts with external interfaces or components.
• Key milestones are traced in the execution path of the application.