```markdown
Use the timeframe picker in the top-right corner to select the time interval you want to investigate.
``````markdown
The default timeframe is 4 hours.
Drag the cursor over an area on the timeline to zoom in on a specific period.
The dashboard automatically applies the timeframe selection to the [metrics](using-sessions-overview.md#metrics "mention") graph.
<div data-gb-custom-block data-tag="hint" data-style='info'>
The system preserves the selected timeframe across all tabs.
</div>
```markdown
セッション概要のタブ
```markdown
The following tabs are available in the Sessions overview dashboard:
[sessions](using-sessions-overview.md#sessions "mention") displays metrics and per-session trends for all VDI sessions to identify issue patterns.
[session-map](using-sessions-overview.md#session-map "mention") displays an overview of connections between the endpoint devices and VMs.
[executions](using-sessions-overview.md#executions "mention") displays a list of all executions on the VMs in all active sessions.
[connections](using-sessions-overview.md#connections "mention") displays an overview of connections between the VMs and backend systems in all sessions.
The following sections explain the components and functionalities of each tab.
```markdown
セッション
```markdown
The **Sessions overview** tab allows you to investigate all active and inactive sessions in your environment.
Use the following filters at the top of the page to view relevant sessions:
**Username** of the client to focus on a single user
**Virtual machine name** to which the clients connect
**Desktop pool name** to which the clients connect
**Environment name** to which the desktop pools belong
バーグラフには最大で2日間の時間枠を選択して表示できます。 ```markdown
The resolution of the chart is affected by the timeframe picker in the following way:```
| 解像度 | 間隔 | 時間枠 |
| --- | ------ | ----- |
| 30秒 | 1時間 | 過去2日 |
| 5分 | 1—8時間 | 過去30日 |
| 15分 | 8—48時間 | 過去30日 |
#### 例
以下の図は、過去30日間の任意の6時間の間隔で5分の解像度を示しています。
<figure><img src="../../.gitbook/assets/sessions-overview-5-minutes.png" alt="5-minute resolution example"><figcaption></figcaption></figure>
しかし、<b>1</b>時間間隔を過去<b>2</b>日間選択すると、<b>30</b>秒の細かい解像度が表示されます：
<figure><img src="../../.gitbook/assets/sessions-overview-30-seconds.png" alt="30-second resolution example"><figcaption></figcaption></figure>
#### ゲージとバー チャートの色コード
```markdown
Hover over the gauge or chart to see a breakdown of session health percentages as a tooltip.
``````markdown
The colors on both the gauge and bar chart indicate the following statuses:
**Green** indicates periods when the sessions had good health.
**Yellow** indicates periods when the sessions had average health.
**Red** indicates periods when the sessions had bad health.
The following sections explain how to use the widgets on this dashboard to narrow down troubleshooting to specific sessions.
内訳 - By ドロップダウンリストを使用して、特定のプロパティごとにメトリックを分類します。 ```markdown
Select a breakdown to apply it as a filter, which will also be visible in the filter menu at the top of the dashboard.```
フィルタリング
フィルタリングを有効にするには、ヘルスサブグループのアクションメニューを選択してください。 ```markdown
The selected filter is visible in the filter menu at the top of the dashboard.```
ヘルスサブグループフィルターはセッション リストにも影響し、フィルターの範囲に含まれるセッションのみがリストに表示されます。
**Session name** to which the client is connected; select a session name to access [**Session view**](using-session-view.md).
**Username** of the client.
**Client device name** used by the client.
**Device -> Name** of the device that is hosting the session; select a device name to access **Device view**.
セッションのセッション状態は、アクティブか切断されています。
最後のユーザー操作が行われた時刻スタンプを示す最終操作時間。
Active metrics in the **Metrics** section are also visible as columns on the right side of the list.
```markdown
セッションビューとデバイスビューへのアクセス
```markdown
Select a session name to access the **Session view** dashboard.
``````markdown
See the [Session view](using-session-view.md) section to learn how to examine details of a specific session to assist in troubleshooting.
Select **Client device name** or **Device -> Name** to access [**Device view**](../device-view/) for the endpoint device or the VM respectively.
```markdown
セッションマップ
```markdown
The **Session map** tab gives you a visual representation of the connection between endpoint devices and VMs across all sessions.
Connection issues can occur across different devices, users and destinations.
``````markdown
Session map accelerates troubleshooting and helps you identify the appropriate team to fix network-related issues by providing an interactive visualization of `session.vdi_events` data.
セッションの使用
Session map breaks down the selected metrics for `session.vdi_events` into multiple properties and uses connection paths to display the relationships between properties.
``````markdown
Nodes and lines represent these relationships.
The Session map connection paths display four columns by default, allowing you to click on nodes or lines to [drill down](using-sessions-overview.md#networkview-drillingdowntospecificfieldsdrilldownclicking) to lower levels of breakdowns.
To switch from the displayed metrics and begin troubleshooting issues:
Select the Display drop-down above the Session map visualization.
2. ```markdown
Select one of the available metrics for the particular connection data set.
```markdown
ビジュアル比較のためのラインの太さ
```markdown
The thickness of a line, which connects two nodes, is proportional to the metric value between those respective nodes when compared to the same metric values between different nodes in the same two columns.
<div data-gb-custom-block data-tag="hint" data-style='info'>
When viewing issue-related metrics, thick lines help you identify the most problematic areas.
</div>
```markdown
ノード
```markdown
The system sorts nodes in descending order within each column.
``````markdown
This makes it likely that thicker lines appear towards the top, but this is not always true.
Session map shows the top eight nodes in each column.
``````markdown
If a column has more than eight nodes, the values are aggregated into the **Others** node at the bottom of the column:
Click on **More** to open another eight nodes in a column.
Click **Less** to hide additional nodes.
<div data-gb-custom-block data-tag="hint" data-style='info'>
To facilitate data interpretation, each node is associated with all paths going through it.
</div>
リーフカウントは、各列の列名の隣にも表示されます。
```markdown
ノードまたはラインにカーソルを合わせる
```markdown
Hover over a node or a line to highlight the connection metric value that goes through that node or line.
```markdown
特定のフィールドを深掘りする
```markdown
Session map displays four columns by default.
``````markdown
Each column is associated with a hierarchy of fields to reduce the number of nodes shown on the screen.
The following table lists the hierarchy of fields for each column, which goes from general to specific:
```markdown
Column 1: ユーザー
```
```markdown
Column 2: クライアントデバイス
```
```markdown
Column 3: デスクトッププール
```
```markdown
Column 4: 仮想マシン
```
```markdown
AD -> 部署
```
```markdown
国の所在地
```
```markdown
仮想化 -> デスクトップブローカー
```
```markdown
仮想化 -> ハイパーバイザー名
```
ユーザー名
```markdown
州の所在地
```
```markdown
仮想化 -> 環境名
```
```markdown
仮想化ホスト名
```
```markdown
クライアントデバイス名
```
```markdown
VDIセッション -> デスクトッププール
```
```markdown
デバイス -> 名前
```
To drill down on a Session map field, you have the following options:
Click on a [node](using-sessions-overview.md#selecting-a-node) in the Session map visualization.
Click on a [line](using-sessions-overview.md#selecting-a-line) between two nodes.
After clicking on a node or line, [navigate back up the hierarchy](using-sessions-overview.md#navigating-back-up-the-hierarchy) using the expandable drop-downs in each column heading in Session map.
```markdown
ノードの選択
```markdown
Select a node to:
Apply a filter for the selected node.
Drill down one level in the column hierarchy.
```markdown
ラインの選択
```markdown
Select a line to:
Apply a filter for the selected line, which is equivalent to selecting the two nodes it connects.
Drill down one level in the hierarchy of the connected columns.
```markdown
階層のナビゲート
```markdown
To navigate back up the hierarchy of the Session map fields after selecting nodes or lines:
Select the drop-down in the Session map column heading.
2. ```markdown
Select any field name above the current level in the hierarchy.
```markdown
接続タイムライン
```markdown
The **Connections timeline** displays the selected metric’s development over time.
``````markdown
For example, if you select **Network RTT**, it shows the number of failed connections across the timeframe selected in the timeframe picker.
The timeline is synchronized with the connection paths.
``````markdown
When you drill down or up on nodes, the timeline chart updates accordingly.
```markdown
タイムラインを使用して期間をズーム
```markdown
The **Connections timeline** is interactive.
``````markdown
To focus on a specific period of interest, click and drag your cursor over that timeframe in the timeline.
This action loads both the Session map chart and the timeline for that period, allowing you to analyze connections data during that time.
<div data-gb-custom-block data-tag="hint" data-style='info'>
Currently, dragging to select a period on the timeline does NOT update the timeframe picker at the top of the page.
</div>
``````markdown
To align the displayed data with the selection in the timeframe picker, click the **Reset timeframe** button located above the **Connections timeline**.
```markdown
実行
```markdown
See a list of all binary executions on VMs in all active sessions.
Select a device name in the **Device -> Name** column to access [**Device view**](../device-view/) for the specific VM.
```markdown
アクションメニュー
```markdown
Use the contextual action menu to refine your troubleshooting by allowing different data exploration paths.
In the **Username**, **Device -> Name** and **Binary -> Name** columns, select the action menu on the right side of the selected binary to open a new contextual investigation to **Retrieve all** connected devices, users, or events.
In the **Device -> Name** and **Binary -> Name** columns, **Diagnose** execution crashes or high CPU usage.
In the following columns, select **Drill down to** in the action menu to open a new contextual investigation to further diagnose issues and remediate them using remote actions:
