When you create a query, Splunk AppDynamics produces a holistic metric. Because the queried data comes from different events, the Events Service has to retrieve this segmented data and stitch it together to produce a single metric. The Events Service waits for correlated events to arrive, where the maximum wait time depends on the event type:

• Mobile and Browser Session Events - two minutes.
• Transaction Events - ten seconds.

The wait time resets when the Events Service finds a correlated event.

If an event arrives after the maximum wait time, the event is not stitched together correctly in your query. For example in the following query fieldA and fieldB are separate but correlated events:

select count(*) from transactions where fieldA = "foo" and fieldB = "bar"

The Events Service finds fieldA and waits 10 seconds for a correlated event. If fieldB arrives 15 seconds after fieldA, the Events Services does not correlate both events. The count metric is now inaccurate because the events are not connected.