# Monitoring

## Monitoring

Advantages of using our free service:

* Our monitoring service is working on dedicated server (24/7 online)
* No need to install database (InfluxDB)
* No need to install and configure Grafana Dashboard
* On Grafana dashboard you will find all necessary metrics of your node (we use this monitoring service by ourselves, so we've configured dashboard properly)

## One line installation:

```
. <(wget -qO- https://raw.githubusercontent.com/L0vd/chain-services/main/testnets/pryzm/monitoring/pryzm-monitoring-install.sh)
```

## OR Manual installation of telegraf and monitoring script

Install telegraf

```
sudo apt update
sudo apt -y install curl jq bc

# install telegraf
wget https://dl.influxdata.com/telegraf/releases/telegraf_1.14.1-1_amd64.deb
dpkg -i telegraf_*.deb

sudo systemctl enable --now telegraf
sudo systemctl is-enabled telegraf

# make the telegraf user sudo and adm to be able to execute scripts as pryzm user
sudo adduser telegraf sudo
sudo adduser telegraf adm
sudo -- bash -c 'echo "telegraf ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers'
```

You can check telegraf service status:

```
sudo systemctl status telegraf
```

Status can be not ok with default Telegraf's config. Next steps will fix it.

Get files from this project repo and copy variable script template

```
cd $HOME
mkdir pryzm-testnet-monitoring
cd pryzm-testnet-monitoring
wget https://raw.githubusercontent.com/L0vd/chain-services/main/testnets/pryzm/monitoring/monitor.sh
wget https://raw.githubusercontent.com/L0vd/chain-services/main/testnets/pryzm/monitoring/telegraf.conf
wget https://raw.githubusercontent.com/L0vd/chain-services/main/testnets/pryzm/monitoring/variables.sh
```

```
nano variables.sh
```

Insert your parameters to **variables.sh**:

* full path to pryzm binary to COS\_BIN\_NAME ( check `which d`)
* node PRC port to COS\_PORT\_RPC ( check in file `path_to_pryzm_node_config/config/config.toml`)
* node validator address to COS\_VALOPER ( like `pryzmvaloper********`)

Save changes in variables.sh and enable execution permissions:

```
chmod +x monitor.sh variables.sh
```

Create telegraf service for pryzm-testnet-node monitoring

```
cat > /etc/systemd/system/telegraf_pryzm_testnet.service <<EOL
[Unit]
Description=The plugin-driven server agent for reporting metrics into InfluxDB
Documentation=https://github.com/influxdata/telegraf
After=network.target
[Service]
EnvironmentFile=-/etc/default/telegraf
User=telegraf
ExecStart=/usr/bin/telegraf -config /etc/telegraf/telegraf_pryzm_testnet.conf -config-directory /etc/telegraf/telegraf.d $TELEGRAF_OPTS
ExecReload=/bin/kill -HUP $MAINPID
Restart=on-failure
RestartForceExitStatus=SIGPIPE
KillMode=control-group
[Install]
WantedBy=multi-user.target
EOL
```

Edit telegraf configuration

```
sudo mv /etc/telegraf/telegraf.conf /etc/telegraf/telegraf.conf.orig
sudo mv telegraf_pryzm_testnet.conf /etc/telegraf/telegraf_pryzm_testnet.conf
```

Restart telegraf service

```
sudo systemctl daemon-reload
sudo systemctl enable telegraf_pryzm_testnet
sudo systemctl restart telegraf_pryzm_testnet
```

### Dashboard interface

Dashboard has main cosmos-based node information and common system metrics. There is a description for each metric.

Go to our comunity dashboard and select you node from the server list:

### [Dashboard link](https://monitoring-dashboards.l0vd.com/d/Pryzm_testnet/pryzm-testnet-monitoring-by-l0vd?orgId=1\&refresh=30s\&from=now-1h\&to=now)

![Screenshot\_1](https://user-images.githubusercontent.com/43213686/169405751-8ff53124-e128-4078-8d68-229a18ea4e25.png) ![Screenshot\_2](https://user-images.githubusercontent.com/43213686/169405777-eb9965a5-9fe8-4ecf-944b-4482c41c019b.png)

#### Mon health

Complex parameter can show problem concerning receiving metrics from node. Normal value is "OK"

#### Sync status

Node catching\_up parameter

#### Block height

Latest blockheight of node

#### Time since latest block

Time interval in seconds between taking the metric and node latest block time. Value greater 15s may indicate some kind of synchronization problem.

#### Peers

Number of connected peers

#### Jailed status

Validator jailed status.

#### Missed blocks

Number of missed blocks in 10000 blocks running window. If the validator misses more than 500 blocks, it will end up in jail.

#### Bonded status

Validator stake bonded info

#### Voting power

Validator voting power. If the value of this parameter is zero, your node isn't in the active pool of validators

#### Delegated tokens

Number of delegated tokens

#### Version

Version of d binary

#### Vali Rank

Your node stake rank

#### Active validator numbers

Total number of active validators

#### Other common system metrics: CPU/RAM/FS load, etc.

No comments needed


---

# Agent Instructions: 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:

```
GET https://chain-services.l0vd.com/testnets/pryzm/monitoring.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.