Snapshots Report

Overview

Snapshots report provides information about Snapshots, Segments, Exit Calls, traversed Service Endpoints and Business Data for all Snapshots in APM Applications.

You can also watch this training video:

Snapshots report is produced when:

• Job file included at least one APM application Target.Type=APM
• Metadata is extracted via Input.DetectedEntities=true
• Snapshots are extracted via Input.Snapshots=true
• Report is requested via Output.Snapshots=true

Report File Locations

Snapshots report has the following file name:

Report\Snapshots.<Job File Name>.<Start Date and Time in yyyyMMddHHmm>.<Number Of Hours Spanned By Report>.xlsx

For example:

Snapshots.demo1demo2.ECommerce.2017123001-2017123003.xlsx

Data File Locations

The data for the report is in the following files:

• Report\SNAP\application.snapshots.csv
• Report\SNAP\snapshots.businessdata.csv
• Report\SNAP\snapshots.csv
• Report\SNAP\snapshots.errors.csv
• Report\SNAP\snapshots.exits.csv
• Report\SNAP\snapshots.segments.csv
• Report\SNAP\snapshots.serviceendpoints.csv

Data Schema

Full Size

Report Contents

Data	Pivot
1.Parameters
2.Contents
3.Controllers
4.Appplications
5.Snapshots	5.Snapshots.Type, 5.Snapshots.Timeline
6.Segments	6.Segments.Type, 6.Segments.Timeline
7.Exit Calls	7.Exit Calls.Type, 7.Exit Calls.Errors, 7.Exit Calls.Timeline
8.SEP Calls	8.SEP Calls.Type, 8.SEP Calls.Timeline
9.Errors	9.Errors.Type, 9.Errors.Timeline
10.Business Data	10.Business Data.Type, 10.Business Data.Timeline

1.Parameters

This sheet describes the parameters of the extraction and reporting job that produced this report.

Column	Data Type	Purpose
Controller	URL	Controller that was queried
UserName	String	User that was used to retrieve data from the Controller
Application	String	Name of Application that was queried
ApplicationID	Integer	ID of Application in Controller
ApplicationType	String	Type of the Application

2.Contents

This sheet provides quick access to the contents of this report and provides at-a-glance number of rows in each of the sheet's tables.

Column	Data Type	Purpose
Sheet Name	String	Name of the sheet in the report
Num Entities	Integer	Number of Entities in that sheet
Link	Hyperlink	Link to the sheet in the report

3.Controllers

This sheet provides information about Controllers covered by this report.

Column	Data Type	Purpose
Controller	URL	Controller that was queried
Version	String	Version of the Controller
VersionDetail	String	Full version string of the Controller
NumApps	Integer	Number of all APM Applications registered in the Controller
NumAPMApps	Integer	Number of APM Applications registered in the Controller
NumWEBApps	Integer	Number of WEB Applications registered in the Controller
NumMOBILEApps	Integer	Number of MOBILE Applications registered in the Controller
NumIOTApps	Integer	Number of IoT Applications registered in the Controller
NumSIMApps	Integer	Number of SIM Applications registered in the Controller
NumBIQApps	Integer	Number of BIQ Applications registered in the Controller
NumDBApps	Integer	Number of DB Applications registered in the Controller
ControllerLink	URL	Link to Controller

4.Applications

This sheet provides Snapshot summary information about all Applications in all Controllers covered by this report.

Column	Data Type	Purpose
Controller	URL	Controller that was queried
ApplicationName	String	Name of Application
NumSnapshots	Integer	Total number of Snapshots
NumSnapshotsNormal	Integer	Total number of Snapshots with Normal user experience
NumSnapshotsSlow	Integer	Total number of Snapshots with Slow user experience
NumSnapshotsVerySlow	Integer	Total number of Snapshots with Very Slow user experience
NumSnapshotsStall	Integer	Total number of Snapshots with Stall user experience
NumSnapshotsError	Integer	Total number of Snapshots with Error user experience
HasActivity	Boolean	Whether this Entity had any activity
From	DateTime	Beginning of time range queried, local time
To	DateTime	End of time range queried, local time
FromUtc	DateTime	Beginning of time range queried, UTC time
ToUtc	DateTime	End of time range queried, UTC time
Duration	Integer	Duration of time range queried, in minutes
ApplicationID	Integer	ID of Application in Controller
DetailLink	Hyperlink	Link to the Entity Details report
ControllerLink	URL	Link to Controller for this time range
ApplicationLink	URL	Link to Application in Controller for this time range

5.Snapshots

This sheet provides summary information about all Snapshots that occurred in the specified time range in all Applications in all Controllers covered by this report.

Column	Data Type	Purpose
Controller	URL	Controller that was queried
ApplicationName	String	Name of Application
TierName	String	Name of Tier where this Business Transaction started
TierType	String	Type of Tier where this Business Transaction started
NodeName	String	Name of Node where this Business Transaction started
AgentType	String	Type of Agent reporting to this Tier
BTName	String	Name of Business Transaction
BTType	String	Type of Business Transaction
UserExperience	String	User Experience (NORMAL, SLOW, VERY_SLOW, STALL, ERROR)
RequestID	GUID	Unique ID of this Snapshot
Occurred	DateTime	When Snapshot was taken, local time
OccurredUtc	DateTime	When Snapshot was taken, UTC time
Duration	Integer	Total duration of Snapshot, in milliseconds
DurationRange	String	String representing bucket into which Duration fits. See Duration Ranges
EndToEndDuration	Integer	Calculated duration of snapshot from beginning of the earliest Segment to end of Last one
DurationEndToEndRange	String	String representing bucket into which EndToEndDuration fits
IsEndToEndDurationDifferent	Boolean	Whether EndToEndDuration is different than Duration
URL	String	URL of original request, if it was a web transaction
CallChains	String	Multi-line representation of all the calls between Tiers, Backends and Applications that occurred. See Call Chains
ExitTypes	String	List of Exit Types and number of calls made by all Segments during entire execution of Snapshot
CallGraphType	String	Type of Call Graph (FULL, PARTIAL, NONE)
IsArchived	Boolean	Whether Snapshot is archived
HasErrors	Boolean	Whether Snapshot has errors
NumErrors	Integer	Number of Errors in all Segments of this Snapshot, if it has Errors
DiagSessionID	GUID	Diagnostic Session ID, if this snapshot was started by one
TakenSummary	String	Summary narrative for why the Snapshot was taken
TakenReason	String	Reason the Snapshot was taken
NumSegments	Integer	Number of Segments in Snapshot
NumCallGraphs	Integer	Number of Segments that have a Call Graph in this Snapshot
NumCalledBackends	Integer	Number of called Backends by all the Segments in this Snapshot
NumCalledTiers	Integer	Number of called Tiers by all the Segments in this Snapshot
NumCalledApplications	Integer	Number of called Applications by all the Segments in this Snapshot
NumCallsToBackends	Integer	Number of calls to Backends by all the Segments in this Snapshot
NumCallsToTiers	Integer	Number of calls to Tiers by all the Segments in this Snapshot
NumCallsToApplications	Integer	Number of calls to Applications by all the Segments in this Snapshot
NumSEPs	Integer	Number of SEPs crossed by all Segments in this Snapshot
NumHTTPDCs	Integer	Number of Business Data entries that were collected via HTTP Data Collectors by all Segments in this Snapshot
NumMIDCs	Integer	Number of Business Data entries that were collected via MIDCs by all Segments in this Snapshot
ApplicationID	Integer	ID of Application in Controller
TierID	Integer	ID of Tier in Application
NodeID	Integer	ID of Node in Application
BTID	Integer	ID of Business Transaction in Application
SnapshotLink	URL	Link to Snapshot in the Controller

5.Snapshots.Type

This sheet uses data in 5.Snapshots sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides breakdown of Snapshots by Business Transaction and summarized by User Experience in all Controllers, Applications and Tiers.

Columns	Rows	Values	Filters
UserExperience
	Controller
	ApplicationName
	AgentType
	TierName
	BTName
		RequestID (Count)
			HasErrors
			CallGraphType
			DurationRange

Here is an example of 5K+ Snapshots grouped by Business Transaction and broken out by User Experience:

Full Size

5.Snapshots.Timeline

This sheet uses data in 5.Snapshots sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides per-minute summary of Snapshots by User Experience.

Columns	Rows	Values	Filters
UserExperience
	Occurred
		Duration (Average)
			Controller
			ApplicationName
			TierName
			BTName
			HasErrors
			CallGraphType
			DurationRange

In this example, we are showing comparisons between 6PM and 7PM for the events broken out by Severity:

Full Size

Filtering on UserExperience=VERY_SLOW and DurationRange:12: 20000<t<=50000, we can see results per hour, clearly showing that those kinds of events are happening in early minutes of 6PM:

Full Size

6.Segments

This sheet provides summary information about all Segments in all Snapshots that occurred in the specified time range in all Applications in all Controllers covered by this report.

Column	Data Type	Purpose
Controller	URL	Controller that was queried
ApplicationName	String	Name of Application
TierName	String	Name of Tier where this Business Transaction started
TierType	String	Type of Tier where this Business Transaction started
NodeName	String	Name of Node where this Business Transaction started
AgentType	String	Type of Agent reporting to this Tier
BTName	String	Name of Business Transaction
BTType	String	Type of Business Transaction
UserExperience	String	User Experience (NORMAL, SLOW, VERY_SLOW, STALL, ERROR) of Segment
SnapshotUserExperience	String	User Experience (NORMAL, SLOW, VERY_SLOW, STALL, ERROR) of Snapshot
RequestID	GUID	Unique ID of this Snapshot
SegmentID	Integer	Unique ID of this Segment in this Snapshot
FromSegmentID	Integer	The Segment that initiated call to this Segment. 0 if this Segment is the originating Segment
FromTierName	String	The Tier of Segment that initiated call to this Segment
Occurred	DateTime	When Segment was taken, local time
OccurredUtc	DateTime	When Segment was taken, UTC time
Timeline	String	Execution timeline. See Segment Timeline
TimelineResolution	Integer	Duration of one character in Timeline in milliseconds. One of the following values: 10, 50, 100, 250, 500, 1000
Duration	Integer	Duration of Segment, in milliseconds
DurationRange	String	String representing bucket into which Duration fits
CPUDuration	Integer	CPU time spent executing this Segment
WaitDuration	Integer	Time spent waiting
BlockDuration	Integer	Time spent blocked by something else
E2ELatency	Integer	End to end latency, for times when you have async invocations
URL	String	URL of original request, if it was a web transaction
CallChains	String	Multi-line representation of all the calls to Tiers, Backends and Applications that occurred in this Segment
ExitTypes	String	List of Exit Types and number of calls made by this Segments during execution
UserPrincipal	String	User that was associated with this execution
HTTPSessionID	String	HTTP Session ID, if this call was HTTP based and it was available
ThreadID	Integer	Thread ID of the executing thread
ThreadName	String	Name of executing thread
CallGraphType	String	Type of Call Graph (FULL, PARTIAL, NONE)
IsArchived	Boolean	Whether this Segment is archived
IsAsync	Boolean	Whether this Segment has async activity
IsFirstInChain	Boolean	Whether this Segment first in the chain of all Segments in Snapshot
HasErrors	Boolean	Whether this Segment has Errors
NumErrors	Integer	Number of Errors in this Segment, if it has Errors
DiagSessionID	GUID	Diagnostic Session ID, if this snapshot was started by one
TakenSummary	String	Summary narrative for why the Segment was taken
TakenReason	String	Reason the Segment was taken
TakenPolicy	String	Reason the Segment was taken
IsDelayedDeepDive,	Boolean	Was this Segment part of delayed deep dive policy
DelayedDeepDiveOffSet	String	Offset from the beginning of snapshot if there was a delayed deep dive
WarningThreshold	String	Dynamic baseline threshold for Warning managed by agent that took this Segment
CriticalThreshold	String	Dynamic baseline threshold for Critical managed by agent that took this Segment
NumCalledBackends	Integer	Number of called Backends by this Segment
NumCalledTiers	Integer	Number of called Tiers by this Segment
NumCalledApplications	Integer	Number of called Applications by this Segment
NumCallsToBackends	Integer	Number of calls to Backends by this Segment
NumCallsToTiers	Integer	Number of calls to Tiers by this Segment
NumCallsToApplications	Integer	Number of calls to Applications by this Segment
NumSEPs	Integer	Number of SEPs crossed by this Segment
NumHTTPDCs	Integer	Number of Business Data entries that were collected via HTTP Data Collectors by this Segment
NumMIDCs	Integer	Number of Business Data entries that were collected via MIDCs by this Segment
ApplicationID	Integer	ID of Application in Controller
TierID	Integer	ID of Tier in Application
NodeID	Integer	ID of Node in Application
BTID	Integer	ID of Business Transaction in Application
SegmentLink	URL	Link to Segment in the Controller

6.Segments.Type

This sheet uses data in 6.Segments sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides breakdown of Segments by Business Transaction and summarized by User Experience in all Controllers, Applications and Tiers.

Columns	Rows	Values	Filters
UserExperience
	Controller
	ApplicationName
	AgentType
	TierName
	BTName
		SegmentID (Count)
			HasErrors
			CallGraphType
			DurationRange

Here is an example of 13K+ Segments grouped by Business Transaction and broken out by User Experience:

Full Size

6.Segments.Timeline

This sheet uses data in 6.Segments sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides per-minute summary of Snapshots by User Experience.

Columns	Rows	Values	Filters
UserExperience
	Occurred
		Duration (Average)
			Controller
			ApplicationName
			TierName
			BTName
			HasErrors
			CallGraphType
			DurationRange

In this example, we are showing comparisons between 6PM and 7PM for the events broken out by Severity:

Full Size

Filtering on UserExperience=ERROR, HasErrors=TRUE and CallGraphType=PARTIAL, we can see results per hour, clearly showing that those kinds of events are happening in early minutes of 6PM:

Full Size

7.Exit Calls

This sheet provides summary information about all Exit Calls made by all Segments in all Snapshots that occurred in the specified time range in all Applications in all Controllers covered by this report.

Column	Data Type	Purpose
Controller	URL	Controller that was queried
ApplicationName	String	Name of Application
TierName	String	Name of Tier where this Business Transaction started
TierType	String	Type of Tier where this Business Transaction started
NodeName	String	Name of Node where this Business Transaction started
AgentType	String	Type of Agent reporting to this Tier
BTName	String	Name of Business Transaction
BTType	String	Type of Business Transaction
SegmentUserExperience	String	User Experience (NORMAL, SLOW, VERY_SLOW, STALL, ERROR) of Segment
SnapshotUserExperience	String	User Experience (NORMAL, SLOW, VERY_SLOW, STALL, ERROR) of Snapshot
RequestID	GUID	Unique ID of this Snapshot
SegmentID	Integer	Unique ID of this Segment in this Snapshot
SequenceNumber	Integer	Snapshot/Segment Sequence counter
ToEntityName	String	Name of Entity that this call was made to
ToEntityType	String	Type of Entity that this call was made to
ToSegmentID	Integer	Segment ID of where the call is going to
Occurred	DateTime	When Segment was taken, local time
OccurredUtc	DateTime	When Segment was taken, UTC time
Duration	Integer	Duration of Exit Call, in milliseconds, for all calls in this line
DurationRange	String	String representing bucket into which Duration fits
AvgDuration	Integer	Duration of Exit Call, in milliseconds, for single call. Different from Duration if NumCalls > 0
ExitType	String	Type of Exit Call
Detail	String	Detail information of the Exit Call
Framework	String	Type of framework as determined by indexing process using mapping from MethodNamespaceTypeMapping.csv
Method	String	Method that made the Exit Call
IsAsync	Boolean	Whether this Exit Call was asynchronous
URL	String	URL of original request, if it was a web transaction
CallChain	String	Single-line representation of the call chain
NumCalls	Integer	Number of calls made by this method
HasErrors	Boolean	Whether this Segment has Errors
ErrorDetail	String	Detail of the Error, if it happened
SQLClauseType	String	For Type=JDBC, DB and ADODOTNET, Type of SQL clause DML: SELECT, INSERT, UPDATE, DELETE, TRUNCATE; DDL: CREATE, ALTER, DROP; Security: GRANT, REVOKE; Stored Procedures: PROCCALL
SQLJoinType	String	Join types: INNER, LEFT, RIGHT, FULL, SELF, CROSS
SQLGroupBy	Boolean	Whether GROUP BY clause is present
SQLHaving	Boolean	Whether HAVING clause is present
SQLOrderBy	Boolean	Whether ORDER BY clause is present
SQLUnion	Boolean	Whether UNION clause is present
SQLWhere	Boolean	Whether WHERE clause is present
SQLTable	String	Name of the SQL Table affected by this query
SQLTables	String	List of the SQL Tables affected by this query if there were more than one
NumSQLTables	Integer	Number of the SQL Tables affected by this query if there were more than one
URLCleaned	String	For Type=URL, WEB_SERVICE and WCF, Cleaned up version of URL with any GUIDs removed
URLScheme	String	URL scheme
URLHost	String	URL host
URLPort	String	URL port
URLPath	String	URL path
URLQuery	String	URL query string
URLFragment	String	URL fragment
URLNumQueryParams	Integer	Number of URL query string parameters
NumProps	Integer	Number of properties associated with Exit Call
PropQueryType	String	Value of QueryType property
PropStatementType	String	Value of StatementType property
PropURL	String	Value of URL property
PropServiceName	String	Value of ServiceName property
PropOperationName	String	Value of OperationName property
PropName	String	Value of Name property
PropAsync	String	Value of Async property
Prop#Name (1-5)	String	Name of property
Prop#Value (1-5)	String	Value of property
PropsAll	String	Name/value pairs for exits, separated by ;, raw data from the values above
ApplicationID	Integer	ID of Application in Controller
TierID	Integer	ID of Tier in Application
NodeID	Integer	ID of Node in Application
BTID	Integer	ID of Business Transaction in Application
ToEntityID	Integer	ID of Entity that was called

7.Exit Calls.Type

This sheet uses data in 7.Exit Calls sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides breakdown of Exit Calls by Type, groups them by their Business Transaction and summarized by Number of Calls, Average Duration and Total Duration.

Columns	Rows	Values	Filters
	ExitType
	Detail
	Controller
	ApplicationName
	TierName
	BTName
		Calls (Sum)
		Duration (Average)
			ToEntityType
			ToEntityName
			RequestID
			DurationRange

Here is an example showing JDBC calls of type Query with Average duration, Total Duration and Number of calls:

Full Size

7.Exit Calls.Errors

This sheet uses data in 7.Exit Calls sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides breakdown of Exit Calls by Errors, groups them by their Business Transaction and summarized by Number of Calls, Average Duration and Total Duration.

Columns	Rows	Values	Filters
	ExitType
	ErrorDetail
	Detail
	Controller
	ApplicationName
	TierName
	BTName
		Calls (Sum)
		Duration (Average)
			ToEntityType
			ToEntityName
			RequestID
			DurationRange
			HasErrors

Here is an example showing JDBC calls of type Query with Average duration, Total Duration and Number of calls:

Full Size

7.Exit Calls.Timeline

This sheet uses data in 7.Exit Calls sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides per-minute summary of calls by the Exit Type.

Columns	Rows	Values	Filters
ExitType
	Occurred
		Duration (Average)
			Controller
			ApplicationName
			TierName
			BTName
			ToEntityType
			ToEntityName
			DurationRange
			Detail

Once you do, here is an example showing Average duration of all types of exit call calls in 2 hour range:

Full Size

Filtering on the JDBC exit type and expanding the time, the report looks a bit more detailed:

Full Size

8.SEP Calls

This sheet provides summary information about all Service Endpoints crossed by all Segments in all Snapshots that occurred in the specified time range in all Applications in all Controllers covered by this report.

Column	Data Type	Purpose
Controller	URL	Controller that was queried
ApplicationName	String	Name of Application
TierName	String	Name of Tier where this Business Transaction started
TierType	String	Type of Tier where this Business Transaction started
NodeName	String	Name of Node where this Business Transaction started
AgentType	String	Type of Agent reporting to this Tier
BTName	String	Name of Business Transaction
BTType	String	Type of Business Transaction
SegmentUserExperience	String	User Experience (NORMAL, SLOW, VERY_SLOW, STALL, ERROR) of Segment
SnapshotUserExperience	String	User Experience (NORMAL, SLOW, VERY_SLOW, STALL, ERROR) of Snapshot
RequestID	GUID	Unique ID of this Snapshot
SegmentID	Integer	Unique ID of this Segment in this Snapshot
Occurred	DateTime	When Service Endpoint was called, local time
OccurredUtc	DateTime	When Service Endpoint was called, UTC time
SEPName	String	Name of Service Endpoint that was called
SEPType	String	Type of Service Endpoint
ApplicationID	Integer	ID of Application in Controller
TierID	Integer	ID of Tier in Application
NodeID	Integer	ID of Node in Application
BTID	Integer	ID of Business Transaction in Application
SEPID	Integer	ID of Service Endpoint that was called

8.SEP Calls.Type

This sheet uses data in 8.SEP Calls sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides breakdown of Service Endpoint Calls by Service Endpoint Type, groups them by their Business Transaction and summarized by Number of Calls.

Columns	Rows	Values	Filters
	Controller
	ApplicationName
	AgentType
	TierName
	BTName
	SEPName
		SegmentID (Count)
			RequestID

Here is an example showing Service Endpoint Calls across multiple Controllers:

Full Size

Here are all the SERVLET Service Endpoint across 10 Applications across 2 Controllers, broken out by frequency of calls:

Full Size

And here is comparison of number of calls to specific Service Endpoint between 2 Applications in 2 Controllers:

Full Size

8.SEP Calls.Timeline

This sheet uses data in 8.SEP Calls sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides per-minute summary of count of Service Endpoint Types.

Columns	Rows	Values	Filters
SEPType
	Occurred
		SegmentID (Count)
			Controller
			ApplicationName
			TierName
			BTName

Once you do, here is an example showing Average duration of all types of Service Endpoint Calls that occurred in 2 hour range:

Full Size

Filtering on SERVLET type, and expanding the time ranges, we see the following:

Full Size

9.Errors

This sheet provides summary information about all Errors that occurred in all Segments in all Snapshots that occurred in the specified time range in all Applications in all Controllers covered by this report.

Column	Data Type	Purpose
Controller	URL	Controller that was queried
ApplicationName	String	Name of Application
TierName	String	Name of Tier where this Business Transaction started
TierType	String	Type of Tier where this Business Transaction started
NodeName	String	Name of Node where this Business Transaction started
AgentType	String	Type of Agent reporting to this Tier
BTName	String	Name of Business Transaction
BTType	String	Type of Business Transaction
SegmentUserExperience	String	User Experience (NORMAL, SLOW, VERY_SLOW, STALL, ERROR) of Segment
SnapshotUserExperience	String	User Experience (NORMAL, SLOW, VERY_SLOW, STALL, ERROR) of Snapshot
RequestID	GUID	Unique ID of this Snapshot
SegmentID	Integer	Unique ID of this Segment in this Snapshot
Occurred	DateTime	When Error occurred, local time
OccurredUtc	DateTime	When Error occurred, UTC time
ErrorName	String	Name of Error that occurred
ErrorType	String	Type of Error
ErrorCategory	String	Category of Error
ErrorMessage	String	Message of the Error parsed from Exception call stack and message
ErrorStack	String	Call stack of the Exception message
ErrorDetail	String	Detail of the Error, including call stack if available
ApplicationID	Integer	ID of Application in Controller
TierID	Integer	ID of Tier in Application
NodeID	Integer	ID of Node in Application
BTID	Integer	ID of Business Transaction in Application
ErrorID	Integer	ID of Error that occurred

9.Errors.Type

This sheet uses data in 9.Errors sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides breakdown of Errors by Type, groups them by their Business Transaction and summarized by number of Errors with specific Message.

Columns	Rows	Values	Filters
	ErrorType
	ErrorName
	ErrorMessage
	Controller
	ApplicationName
	TierName
	BTName
		SegmentID (Count)
			RequestID

Here is an example of Errors summarized by message:

Full Size

9.Errors.Timeline

This sheet uses data in 9.Errors sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides per-minute summary of count of Errors.

Columns	Rows	Values	Filters
ErrorType
	Occurred
		SegmentID (Count)
			Controller
			ApplicationName
			TierName
			BTName
			ErrorName
			ErrorMessage
			ErrorDetail

Here is an example showing Errors in Checkout transaction across multiple Applications in multiple Controllers:

Full Size

10.Business Data

This sheet provides summary information about all Business Data (Data Collectors) that were collected by all Segments in all Snapshots that occurred in the specified time range in all Applications in all Controllers covered by this report.

Column	Data Type	Purpose
Controller	URL	Controller that was queried
ApplicationName	String	Name of Application
TierName	String	Name of Tier where this Business Transaction started
TierType	String	Type of Tier where this Business Transaction started
NodeName	String	Name of Node where this Business Transaction started
AgentType	String	Type of Agent reporting to this Tier
BTName	String	Name of Business Transaction
BTType	String	Type of Business Transaction
SegmentUserExperience	String	User Experience (NORMAL, SLOW, VERY_SLOW, STALL, ERROR) of Segment
SnapshotUserExperience	String	User Experience (NORMAL, SLOW, VERY_SLOW, STALL, ERROR) of Snapshot
RequestID	GUID	Unique ID of this Snapshot
SegmentID	Integer	Unique ID of this Segment in this Snapshot
Occurred	DateTime	When Data Collector was collected, local time
OccurredUtc	DateTime	When Data Collector was collected, UTC time
DataName	String	Name of Data Collector
DataValue	String	Value of Data Collector
DataType	String	Type of Data Collector (Transaction, HTTP, Exit, Code)
ApplicationID	Integer	ID of Application in Controller
TierID	Integer	ID of Tier in Application
NodeID	Integer	ID of Node in Application
BTID	Integer	ID of Business Transaction in Application

10.Business Data.Type

This sheet uses data 10.Business Data sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides breakdown of Exit Calls by Type, groups them by their Business Transaction and summarized by Number of Calls, Average Duration and Total Duration.

Columns	Rows	Values	Filters
DataType
	Controller
	ApplicationName
	AgentType
	TierName
	DataName
		SegmentID (Count)
			RequestID

Here is an example of Business Data, filtered to only show MIDCs (Code), and to only show something starting with "customer, summarized by number of occurrences:

Full Size

10.Business Data.Timeline

This sheet uses data 10.Business Data sheet as source for pivot table to enable summary reporting and ad-hoc drill-down.

Default configuration provides per-minute summary of count of Business Data.

Columns	Rows	Values	Filters
DataType
	Occurred
		SegmentID (Count)
			Controller
			ApplicationName
			TierName
			BTName
			DataName
			DataValue

Here is an example showing all types of Business Data across multiple Applications in multiple Controllers in 2 hours:

Full Size

Filtering on DataType=Code, DataName=customerCity and BTName=Checkout, we can see how frequently this occurred in the 2 hour range:

Full Size

Call Chains

Call chains are displayed for Segments and Snapshots (which as sums of Segments).

Here is an example Call Chain:

(ECommerce-Services)->[HTTP]/[469 ms]-><api.shipping.com>;
(ECommerce-Services)->[HTTP]/[5:(2 ms, 1 ms, 2 ms, 2 ms, 2 ms)]->(Inventory-Services);
(ECommerce-Services)->[JMS]/[2 ms async]-><Active MQ-CustomerQueue>;
(ECommerce-Services)->[JMS]/[5:(2 ms async, 2 ms async, 8 ms async, 3 ms async, 2 ms async)]-><Active MQ-fulfillmentQueue>;
(ECommerce-Services)->[JMS]/[2:(1 ms async, 2 ms async)]-><Active MQ-OrderQueue>;
(ECommerce-Services)->[WEB_SERVICE]/[10:(20 ms, 19 ms, 21 ms, 20 ms, 19 ms, 30 ms, 21 ms, 27 ms, 29 ms, 23 ms)]->(Inventory-Services);
(ECommerce-Services)->[WEB_SERVICE]->(Inventory-Services)->[JDBC]/[13 ms]-><INVENTORY-MySQL DB-DB-5.7.13-0ubuntu0.16.04.2>;

How to read Call Chain:

• Tiers are in parenthesis ()
  • (ECommerce-Services) is a Tier
• Backends are in angle brackets <>
  • <INVENTORY-MySQL DB-DB-5.7.13-0ubuntu0.16.04.2> is a Backend
• Applications are in curly brackets {}
  • {Ecommerce-Fulfillment} is an Application
• Calls between are in square brackets []
  • [HTTP]/[469 ms] is an HTTP call that took 469 ms
• Multiple calls are counted explicity
  • [WEB_SERVICE]/[10:(20 ms, 19 ms, 21 ms, 20 ms, 19 ms, 30 ms, 21 ms, 27 ms, 29 ms, 23 ms)] is a a result of one segment making 10 WEB_SERVICE calls during this Snapshot

Segment Timeline

The Timeline column in Segments is a string representation of the waterfall.

• Every character in the timeline represents an interval of time
• Duration of the time is specified in TimelineResolution column
• "-" dash character represents execution interval
• "^" caret character represents execution interval AND an Exit Call
• Number (1, 2, 10, 20 and so forth) represents number of seconds

Here is an example for TimelineResolution=1000:

^-------^10--------20----^---30--^-----40---------
^-------
         ^-------
                 ^-------
                         ^-------
                                 ^------^
                                          ^-------

How to read Timeline:

• First line represents first segment duration of 50304 ms, with 10, 20, 30 and 40 representing seconds, ^ signs showing Exit Calls early in the call, right before 10 seconds, between 20 and 30 seconds and 30 and 40 seconds
• Other segments are shown below in the waterfall

Duration Ranges

The ExecRange column in Snapshot, Segment and Exit Call is calculated using the Duration of the event.

The dimension calculates using the value of time using the following values:

• -1: t<0
• 00: t=0
• 01: 0<t<=10
• 02: 10<t<=50
• 03: 50<t<=100
• 04: 100<t<=200
• 05: 200<t<=500
• 06: 500<t<=1000
• 07: 1000<t<=2000
• 08: 2000<t<=5000
• 09: 5000<t<=10000
• 10: 10000<t<=15000
• 11: 15000<t<=20000
• 12: 20000<t<=50000
• 13: 50000<t<=100000
• 14: 100000<t<=150000
• 15: 150000<t<=200000
• 16: 200000<t<=300000
• 17: t>300000