Skip to content

monitoring.md

Latest commit

 

History

History
77 lines (52 loc) · 3.21 KB

monitoring.md

File metadata and controls

77 lines (52 loc) · 3.21 KB
Raw

How To Monitor Your Node State

Overview

Monitoring your node's activity is crucial to ensure it's functioning correctly and processing data as expected. This guide will walk you through checking transactions and locating node logs.

Step 1: Check Transactions

Track your node's activity using the peaq Subscan web interface.

Steps:

  1. Visit the peaq Subscan website (e.g., https://peaq.subscan.io/account/YOUR_ADDRESS)
  2. Search for your node's transactions using your Datakeeper address
  3. Check transaction statuses:
    • Green check marks indicate successful transactions, confirming your node is working correctly
    • Regular and stable transactions confirm proper node operation

Transaction Status Indicators

✅ Successful Transactions

Green check marks indicate successful transactions
Successful Transactions

💡 Note: There should be 2 Proof of Storage regular transactions for every running node, one confirms data storage of the whole node file system and another one makes a specific user data snapshot.

⚠️ Single Errors

Occasional single errors are normal - don't worry if previous and subsequent transactions are successful
Single Failure

❌ Multiple Errors

If you see several errors in a row, contact support with Node logs
Failed Transactions

Step 2: Locate Node Logs

Method 1: Using Node Manager Graphical Interface

First way is using the Node Manager application by clicking the Download button
Download Logs

Method 2: File System Explorer

⚠️ Note: logs folder is created when the node runs under DeNode Manager (Desktop or Web). A standalone CLI node prints logs to the terminal only — redirect them to a file if you need to keep them, e.g. ./denode >> denode.log 2>&1 (see CLI install guides).

Windows:

You can find your node logs by entering this line in Windows Explorer:

%USERPROFILE%\.denode\logs

Windows Logs

You'll see log files named after your license numbers.

Linux and macOS:

Node logs are located at:

~/.denode/logs

Method 3: CLI Users

Screenshot the latest logs or a particular errors from your terminal.

If the node runs as a systemd service, it has no terminal and its output goes to journald: journalctl -u denode -n 100.

Log File Information

  • Log files are named according to your license numbers
  • These logs contain detailed information about node operations and any errors that occurred
  • Review logs regularly to identify potential issues before they become critical

Troubleshooting Tips

  • Regular transaction monitoring helps identify issues early
  • Keep an eye on transaction frequency and success rates
  • If you notice persistent errors, consult the logs for detailed error messages
  • Contact support with logs when experiencing multiple consecutive transaction failures