Specific Instructions for using PG3x Logging system?

[someguy]

if someone could point me to some instructions, I'd appreciate it.  

 

otherwise, I'd like to have some simple (embarrassing) questions answered: 

--when I go to the log page, the page is initially blank, then information starts showing up.  is this because it only starts logging when I open it? 

--which of the settings (debug, warning, critical, etc) includes all of the information? 

--is there a dictionary or somewhere that I can read to better understand the log?  what (computer) language is it in?  

[paulbates]

You need to know how to log when you have an plugin issue and developer asks you to send them a log. What's important to know about that is:

• you go to the dashboard in pg3x
• go into the individual plugin itself
• click details
• Click log
• Click "debug" from the list
• Do the steps that recreate the error you are seeing
• Click download log package
• Send that zip file in a message to the developer

 

There's a new wrinkle in the Session and Session Verbose options. I'm going to not select those unless instructed to by the developer.

Edited October 27 by paulbates

[someguy]

@paulbatesOkay, thank you.  much appreciated!

[bpwwer]

3 hours ago, someguy said:

--when I go to the log page, the page is initially blank, then information starts showing up.  is this because it only starts logging when I open it? 

Yes, for plug-in's it doesn't display historical information, just real-time.  The PG3x log itself does display historical information (back to midnight of the current day).  Each daily log is saved for 2 weeks, I believe, but there's no way to view those daily logs via the GUI.

3 hours ago, someguy said:

--which of the settings (debug, warning, critical, etc) includes all of the information?   

debug would show the most information, critical shows the least.  Typically you'd want to have this set to error or warnings.  Those will show (as you might expect) error messages and warning messages.  The plug-in developer determines what messages are shows at each level and there isn't any standard for what messages get shown at what level.  So how useful each level is, depends on the developer.

3 hours ago, someguy said:

--is there a dictionary or somewhere that I can read to better understand the log?  what (computer) language is it in?  

The log messages are supposed to be just human readable text.   Some additional information is included in them by default:  date/time, the log level, the module where the message was generated from.   For the most part, you can ignore all of that.  Here's a breakdown of a log message:

DATE       TIME         Thread Name            Module             LOGLEVEL MESSAGE
2024-10-27 00:00:35.500 Thread-3 (run_forever) udi_interface      DEBUG    picos:btn_callback: Button on was Press