BTM - When Modifying Transactions or the Observer Communication Policy, How Will That Affect The Performance of the Observers and Monitors?
(Doc ID 2099839.1)
Last updated on JANUARY 19, 2023
Applies to:
APM - Application Performance Management - Version 12.1.0.7.0 to 12.1.0.7.0 [Release 12.1]Information in this document applies to any platform.
Goal
When running BTM 12.1.0.7.x, will there be any performance improvements or degradation on the BTM observers based on changes to a transaction, observer configuration setting, etc.?
In other words, what changes can you make in BTM that will affect how the BTM observer or monitor behaves?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| Observer Communication Policy Settings for a BTM Observer |
| Observer Behavior |
| Configuration polling interval [300] Seconds |
| Instrument update interval [60] Seconds |
| Number of connections [2] Connections |
| Discovery processing interval [3] Minutes (1 - 1440) |
| Enable dynamic discovery interval |
| Observer Troubleshooting |
| Enable trace logging Trace logging level |
| Log observed messages to file Observation Log Directory |
| Observer Message Queue |
| Queue size [200] Messages |
| Maximum message size [2048] Kilobytes |
| Monitor Message Queue |
| Queue size [1000] Messages |
| Maximum message size [2048] Kilobytes |
| Idle socket timeout [300000] Milliseconds |
| Retain request messages for a maximum of [60] Seconds |
| Number processing threads handling messages [5] |
| Number processing threads handling endpoint discovery [2] |
| JDB Summary |
| Transaction Processing |
| “Maximum transaction duration” of a transaction (default = 1 minute) |
| A “bare bones” transaction |
| Message properties to connect two operations. |
| Enable an instance and property logging |
| Enable message logging |
| Address and consumer segmentation |
| References |