JENNIFER APM

Download 4
Last updated Oct 30, 2026

X-View Transactions

X-View Transactions is the window that spreads the transactions picked on an X-View chart into a list, and lets you dig into one of them down to its methods, SQL and external calls.

Opening it

It is not on the menu. It opens in a new browser window from:

WhereHow
A dashboard's X-ViewDrag over points, or click the chart and press Ctrl+B (every point)
X-View analysisDrag in the select-an-area mode, press Ctrl+B, or check table rows and click the popup button (팝업으로 보기)
A shared linkOpen an address copied with 현재 화면을 공유하기 (share the current page) in a detail screen

The window opens centered on the window that opened it. A second drag replaces its contents; check 중복 팝업 허용 (allow duplicate popups) in the list's header to get a new window for every drag.

Tip
If no window opens, check that the browser is not blocking popups from the Sonar address. Reloading the window
opens the same list of transactions again.

With many transactions, a circular gauge shows the loading progress first. 이 시점을 기준으로 조회 중단하기 (stop loading here) shows the list with what has arrived so far. When one transaction (or one GUID) was opened, the list is skipped and its detail opens directly.

The list

The screen is the header, the filter panel on the left, and the tabs with their content.

Header

  • Filter button (far left) - opens and closes the filter panel. Its state is remembered in the browser
  • 중복 팝업 허용 (allow duplicate popups) - the new window option above
  • Help - opens the JENNIFER console's manual in a new window

Filter panel

Filters narrow the transactions already received, and all of them apply together. Each change redraws the table, application map, SFR and MSA tabs with the narrowed set.

SectionContents
Time rangePick response, method, SQL, external call or batch time in the dropdown and set the range with the slider. The ↻ button beside it resets every filter
Transaction kindError, MSA root, stack trace, asynchronous, synchronous. Kinds with no transactions are disabled
ApplicationsA checkbox per application, a bar of its method, SQL, external call and batch time shares, and its count
Value listsWhichever of domain, instance, error, client ID, GUID, user ID, client IP and HTTP status have values

Each section has a search box, the number picked (0개 선택됨, "0 selected") and a checklist. Four items show at first; N개 모두 보기 (show all N) unfolds the rest. The arrow by a section's title folds it, and the fold is remembered in the browser.

Tabs

TabContents
Transaction data (트랜잭션 데이터)The transaction table
Application map (애플리케이션 맵)A treemap by application. A tile's size is its calls, its color the active service band the chosen metric falls in. The button at the top right changes the metric
MSAThe call relation tree of linked transactions, with a bar chart
SFRThe stack traces of the listed transactions as a method table and a flame graph
  • Application map - click a tile, or drag across several, to open their transactions as a list on top. Hover over a tile for its calls, errors and times
  • MSA - available only when the opener asked for MSA analysis or every listed transaction is linked. Otherwise it is disabled, with a hint to pick MSA roots in the filter panel. The tree lays out vertically or horizontally; hovering a node highlights it in both the tree and the bar chart. Click an application, DB or external call node to open its transactions as a list
  • SFR - available only when the list is of one domain and holds at most 100,000 transactions. It works like Stacktrace Flight Recorder in Analysis (search, head or tail first, view switch, method table, flame graph)

Transaction table

50 rows a page. Above it are the profile color legend (Method, SQL, External Call, Batch Job, ERROR) and the tools:

  • The page indicator (N개 중 1-50, "1-50 of N") and previous and next page
  • ↻ reset table settings (테이블 설정 초기화) - puts the columns and sorting back as they were
  • Manage columns (테이블 컬럼관리) - choose the columns shown (application, domain, instance, TXID, GUID, client ID and IP, user ID, start and end time, response, method, SQL, external call, batch, fetch, CPU, network and frontend time, HTTP status, error, SQL count and more). The last visible column cannot be turned off
  • ⋯ - export (내보내기, the visible columns as CSV), export all profiles (전체 프로파일 내보내기) and, with AI on, the representative transactions switch (대표 트랜잭션)

Time columns are drawn as bars with their numbers, so you see at a glance how much of the response time went to methods, SQL and external calls. The method time is the response time less the SQL and external call times. Click a column head to sort. Click a row to open that transaction's detail over the list.

The detail

Header

The ← button on the left (or Esc) goes back to the list; beside it is the application name. On the right is a summary: response time, CPU, method, SQL and external call times.

The ⋯ menu has:

  • Share to Talk (토크로 내보내기) - posts this transaction to the console's Talk board (see the caution below)
  • Share the current page (현재 화면을 공유하기) - copies an address pointing at this transaction to the clipboard
  • LIKE search (GUID) (LIKE 검색 (GUID)) - whether the GUID screen matches the GUID partially

The shared address is the address of this app's X-View Transactions window. Whoever opens it must be able to use this app in Sonar, and with several connect profiles the profile choice comes first. The address finds the transaction within 30 minutes either side of its collection time.

Toolbar

The tabs are timeline (타임라인), flame graph (Flame 그래프), call tree (콜 트리), text (텍스트) and MSA. A transaction without profiles opens on the text tab, and the MSA tab is disabled for a transaction without links. The last tab you used is remembered in the browser.

On the right, buttons appear depending on the transaction.

ButtonWhen it appearsWhat it opens
Stack trace (N) (스택트레이스 (N))Stack traces were collectedThe stack trace screen
GUIDIt has a GUIDThe transactions linked by the same GUID
CICSIt has CICS timesThe CICS figures window

Timeline

The transaction's profiles (methods, SQL, external calls, batch jobs, errors, fetches and so on) as bars in time order.

  • Profile list on the left - the frontend box (DOM, network and render times) and the server box (method, SQL and external call times and counts), with socket, file, message and error tabs below. Click a bar in the server box to open a window with that type's calls in a summary or individual table (Raw SQL 보기 for SQL), which can be downloaded as CSV. Click a row of the tabs to jump to that profile. The button at the left of the toolbar shows and hides this list
  • Type chips - Method, SQL, External Call, Batch Job, ERROR and Fetch with their counts. Click one to highlight that type and dim the rest
  • Minimap - drag over the small picture at the top to choose the range in view. The wheel and arrow keys narrow and move it; a double click goes back to the whole time
  • Search (magnifier) - finds profiles by method or SQL text
  • ⋮ - the socket, file and message filters (소켓 표시, 파일 표시, 메시지 표시) and CSV export of the timeline

Click a bar to open the profile layer (below).

Flame graph

The profiles piled by call relation. A box's width is its time, its color its type; a box with an error gets a caution icon. Choose the range with the minimap at the top, and pick head first or tail first for long names. Click a box to open the profile layer.

Call tree

The top is a time bar split into Method, SQL, External Call and Batch Job rows; below it is the call tree table (No., profile name, response time, package, class, CPU time, API and so on).

  • Click a bar at the top, or move with ← and →, to open the tree rows down to that profile and mark them
  • Click a row to open the profile layer
  • Click the number in No. to be asked whether to show that profile on the text tab
  • The column button chooses the columns (the first two always show); ⋮ offers show 0 ms methods (0ms 메서드 표시), show not profiled (Not Profiled 표시), open all nodes (노드 전체 열기) and CSV export

Text

The transaction's information (TXID, times, response, SQL and CPU times, domain, instance, client IP, User-Agent, HTTP status and more) and every profile, in the console's text format. The button at the top right switches between a light and a dark background, and ⋮ downloads it as TXT or CSV.

MSA

The call relations that start at this transaction, as a tree. A folding panel on the right holds a time bar per node, and the layout is vertical or horizontal. Click a node to open that transaction's detail on top; its header then draws the flow from the root to that transaction as circles and bands. Click another circle in the flow to move to that transaction.

Profile layer

Pick a profile on the timeline, the flame graph or the call tree and a layer slides in from the right. It has a type badge at the top and closes with Esc or its close button. Drag its left edge to resize it; the width is remembered in the browser.

TypeContents
MethodThe method, package and class buttons, parameters and return value, the call path, response time against the transaction's, CPU time, errors
SQLThe SQL, inline and bind parameters, the call path, times, errors. At the bottom, the SQL 성능 상세 보기 (SQL performance details) button
External callThe call's description, the call path, times, errors. For an asynchronous call, a button to analyze the called transaction (비동기 트랜잭션 분석하기)
Fetch, error, batch and othersThe call path and that type's values

The call path shows the parents from the top down to this profile, and its children, as bars; click a bar to move to that profile.

클래스 보기 (show class) on a method's class button opens the class window, with decompiled code, class type and disassembled code tabs. Decompiled and disassembled code need the matching permission on the console account.

SQL 성능 상세 보기 is enabled when the SQL ran on a database monitored by Sherpa for Oracle; clicking it opens that SQL's Sherpa for Oracle screen in a new window.

Stack traces, GUID, CICS

  • Stack traces - the detail tab (상세) lists the collection times on the left (the same stacks grouped by color) and shows the picked stack on the right, with the collection interval above. The SFR tab shows the transaction's stacks as a method table and a flame graph. The header's ⋯ has share to Talk and export all stack traces (전체 스택트레이스 내보내기)
  • GUID - the transactions linked by the same GUID, as a timeline by application and a table. Click a transaction on the timeline to find it in the table; click a row to open its detail
  • CICS - bars splitting the wait time into suspend, dispatch and CPU, and the CICS monitoring fields

Actions that change the console

The following leave records on, or change settings of, the JENNIFER server with the profile's console account. Their buttons appear according to the account's permissions, and the table notes which ones ask for confirmation.

ActionWhen it appearsEffect
Method, class and package profile settingsMethod layer, account with the call tree profile setting permissionThe method menu (method profile, exclude method profile, external call, GUID, user ID) saves from a settings window where you pick target instances and parameters. Package and class profiles, and their exclusions, are saved right after a confirmation. The console's call tree profile settings change
Export all profilesTransaction table ⋯After confirmation, a background job is created in the console. Collect the result from 사용자 메뉴 > 나의 배치잡 (user menu > my batch jobs) in the console
Export all stack tracesStack trace screen ⋯After confirmation, a background job is created
Share to TalkDetail header ⋯, stack trace screen ⋯A post is written on the console's Talk board under the profile's account
SQL performance detailsSQL layerAsks the console for the Sherpa for Oracle link
Caution
Profile settings change the console's call tree profile settings, and sharing to Talk leaves posts other console
users see. Give the connect profile a dedicated console account with only the permissions the screens are for.
For reading only, an account without the profile setting permission is the safe choice.

TXT and CSV downloads leave no record in the console.