Operational Monitoring

Operational Monitoring

This fork promotes critical connection events to the standard INFO log level, allowing you to monitor high-volume proxy environments without enabling verbose debugging.

1. Interpreting "High-Signal" Logs

Standard UrNetwork logs are often either too quiet or too "noisy." We have promoted specific events to help you see the "heartbeat" of your node:

• [net][s]select: This represents a successful proxy connection handshake. In a healthy high-volume node, you should see a steady stream of these lines.
• [contract]create: Logs every time a new contract is requested from the signaling layer.
• oob err: Logs signaling failures. See the Troubleshooting Guide for details on specific OOB errors.

2. Integrated Monitoring Tools

vnStat Traffic Monitor

If ENABLE_VNSTAT=true is set (default), you can view real-time and historical traffic statistics via a web interface.

• Access: http://<your-ip>:8080 (or whichever port you mapped to 8080).
• Usage: Useful for identifying traffic spikes or verifying that bandwidth is actually being utilized across your proxy list.

The Stats Script

The container includes a built-in metric exporter located at /app/cgi-bin/stats.

• This provides a raw snapshot of current connection counts and throughput.
• It is used internally by the Pelican Panel integration but can be called manually via docker exec.