How does TIBCO Scribe® Online obtain the GetConnection metrics in the Execution History View Statistics dialog?

• The Duration (ms) is the total time spent on a given operation in milliseconds.  In the image, the total time for the 19 calls for the CRM Dev GetConnection is 221359(ms).
• The Max Time (ms)  is the highest individual call duration out of a set. The longest single GetConnection() call took 46344(ms).
• The Min Time (ms)  is the lowest individual call duration out of a set.  The shortest single GetConnection() call took 0(ms).

How does TIBCO Scribe® Online determine the max time and duration?
 

• The Agent keeps track of the time for each individual call, then adds it to the total (a.k.a Duration (ms) ).  It checks whether the currentCallTime is greater than the currentMaxCallTime. If so, the Agent updates the currentMaxCallTime to the currentCallTime since it has found one that is larger. Essentially each call simply keeps track of its time, then adds it to the total duration.

How can these metrics be affected by TIBCO Scribe® Online? 

• These metrics are a compilation of all operations within a Map.  For example, if you have more Lookup Blocks in your Map, there will be additional rows in the grid.  If you have more Source Rows, then you will have higher target operation counts/Call Counts in the grid.

How else can these metrics be affected?
 

• Variations in GetConnection() times could be due to several factors.  Some potential factors include but are not limited to:
  • Stress on the system/server where the TIBCO Scribe® Online Agent is running -   slow performance, insufficient resources, or  other hardware or software issues.
  • Network traffic - Internet Service, Bottlenecks, packet loss, connection drops,
  • Poor performance from the endpoint, for example CRM itself being slow for some reason.