> For the complete documentation index, see [llms.txt](https://cardano-node-installation.stakepool247.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cardano-node-installation.stakepool247.eu/cardano-relay-configuration/monitoring-with-gliveview.md).

# Monitoring with gLiveView

[gLiveView](https://cardano-community.github.io/guild-operators/Scripts/gliveview/) is a terminal-based monitoring tool from the Guild Operators community. It provides a real-time dashboard showing node status, sync progress, peer connections, block propagation, and resource usage.

## Installation

Download gLiveView and its environment config file:

```bash
mkdir -p $HOME/.local/logs
curl -sL -o $HOME/.local/bin/gLiveView.sh \
  https://raw.githubusercontent.com/cardano-community/guild-operators/refs/heads/alpha/scripts/cnode-helper-scripts/gLiveView.sh
curl -sL -o $HOME/.local/bin/env \
  https://raw.githubusercontent.com/cardano-community/guild-operators/refs/heads/alpha/scripts/cnode-helper-scripts/env
chmod 755 $HOME/.local/bin/gLiveView.sh
```

## Configuration

The default `env` file expects paths at `/opt/cardano/cnode`. Update it to match this guide's layout:

```bash
sed -i "s|#CNODE_HOME=.*|CNODE_HOME=\"/home/cardano/cnode\"|" $HOME/.local/bin/env
sed -i "s|#CNODE_PORT=.*|CNODE_PORT=3001|" $HOME/.local/bin/env
sed -i 's|#CONFIG=.*|CONFIG="${CNODE_HOME}/config/config.json"|' $HOME/.local/bin/env
sed -i 's|#SOCKET=.*|SOCKET="${CNODE_HOME}/sockets/node.socket"|' $HOME/.local/bin/env
sed -i 's|#TOPOLOGY=.*|TOPOLOGY="${CNODE_HOME}/config/topology.json"|' $HOME/.local/bin/env
```

Verify the settings:

```bash
grep -E "^(CNODE_HOME|CNODE_PORT|CONFIG|SOCKET|TOPOLOGY)" $HOME/.local/bin/env
```

Expected output:

```
CNODE_HOME="/home/cardano/cnode"
CNODE_PORT=3001
CONFIG="${CNODE_HOME}/config/config.json"
SOCKET="${CNODE_HOME}/sockets/node.socket"
TOPOLOGY="${CNODE_HOME}/config/topology.json"
```

## Usage

With your node running, launch gLiveView:

```bash
gLiveView.sh
```

The dashboard shows:

| Section               | Information                                     |
| --------------------- | ----------------------------------------------- |
| **Header**            | Node name, network, uptime, port, version       |
| **Epoch**             | Current epoch, progress bar, time remaining     |
| **Block/Slot**        | Current block, slot, tip reference, sync status |
| **Connections**       | P2P peer stats, incoming/outgoing connections   |
| **Block propagation** | Last block time, propagation percentiles        |
| **Resource usage**    | CPU, memory, disk I/O, process stats            |

{% hint style="info" %}
Press **Q** to quit gLiveView. Press **P** for peer analysis view.
{% endhint %}

## Install on all nodes

Install gLiveView on each of your relay and BP servers — it is a read-only monitoring tool and safe to run on any node.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cardano-node-installation.stakepool247.eu/cardano-relay-configuration/monitoring-with-gliveview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.