This commit is contained in:
SpudGunMan
2024-10-04 21:03:58 -07:00
parent c42b6cccb1
commit 99b4e5a1b5
3 changed files with 8 additions and 4 deletions

View File

@@ -22,7 +22,7 @@ The bot can also be used to monitor a radio frequency and let you know when high
Any messages that are over 160 characters are chunked into 160 message bytes to help traverse hops, in testing, this keeps delivery success higher.
But wait there is more! There is a nice data reporting html generator for reatime glance at the bot traffic and data flows!
But wait there is more! There is a nice [data reporting](logs/README.md) html generator for reatime glance at the bot traffic and data flows!
## Full list of commands for the bot

BIN
etc/reporting.jpg Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 124 KiB

View File

@@ -1,5 +1,11 @@
Logs will collect here.
Reporting is via [etc/report_generator5.py](etc/report_generator5.py), run it from the etc/ working directory. The report_generator5 has newer feel and HTML5 coding. The index.html output is published in [../etc/www](../etc/www)
- Make sure to have `SyslogToFile = True` to use reporting! ‼️
- serviceTimer templates for routine output
![reportView](../etc/reporting.jpg)
Logging messages to disk or Syslog to disk uses the python native logging function. Take a look at the [/modules/log.py](/modules/log.py) you can set the file logger for syslog to INFO for example to not log DEBUG messages to file log, or modify the stdOut level.
```
[general]
@@ -12,6 +18,4 @@ Example to log to disk only INFO and higher (ignore DEBUG)
```
*log.py
file_handler.setLevel(logging.INFO) # DEBUG used by default for system logs to disk example here shows INFO
```
Reporting is via [etc/report_generator5.py](etc/report_generator5.py) static log analysis to a HTML report file.
```