Logging Explained - Revision history

Mparadis: Redirected page to Phidget Logging

2023-08-03T20:29:56Z

← Older revision		Revision as of 20:29, 3 August 2023
Line 1:		Line 1:
	[[~~Category:~~Logging]]		#REDIRECT [[Phidget Logging]]
	~~__TOC__~~

	~~==Logging==~~

	~~Logging is a set of functionality designed to quietly track the operation of a software program to be stored for later examination. It is generally used for debugging purposes.~~

	~~==Getting Started==~~

	~~For basic use of the log class, the only functions you need to worry about are <code>enable</code> and <code>log</code>.~~

	~~Simply <code>enable</code> logging with log level <code>INFO</code>, and use <code>log</code> to write your own messages to the log file.~~

	~~This usage is covered in the Log examples, available for the core languages.~~

	~~==Anatomy of a Log==~~

	~~To better understand the concepts in this guide, we will dissect a log entry to clarify its component parts.~~

	~~[[Image:Log_Anatomy.png\|link=\|center]]~~

	~~===Source===~~
	Sources are a property of Phidgets Log messages that indicate where the log message originated. By default, the writing to the log using the <code>log</code> function of your language will write to the source named '''phidget22'''.

	~~For more advanced applications, some log functions will allow you to specify custom sources to allow for specialized logging implementations.~~

	~~====Hidden Sources====~~
	In addition to the default phidget22 source, there are a number of background log sources that are hidden by default. This is to keep log files relatively clean and allow focus on messages that matter to the application.

	~~These sources are:~~
	~~{\| class="wikitable" style="width: 700px;"~~
	\|-
	~~\| _phidget22bridge~~
	~~\| '''Internal Use''' Phidget Bridge Logs (Not the physical device)~~
	\|-
	~~\| _phidget22channel~~
	~~\| '''Internal Use''' Channel Information Logs~~
	\|-
	~~\| _phidget22disp~~
	~~\| '''Internal Use''' Phidget Dispatch Logs~~
	\|-
	~~\| _phidget22match~~
	~~\| '''Internal Use''' Channel Matching Logs~~
	\|-
	~~\| phidget22netctl~~
	~~\| Network Control Logs~~
	\|-
	~~\| phidget22usb~~
	~~\| USB Processing Logs~~
	\|-
	~~\| phidget22net~~
	~~\| Network Logs~~
	\|}

	~~===Log Level===~~
	~~Log levels are designed to sort messages in terms of importance, with lower log levels being generally the most important, and higher log levels carrying supplemental information.~~

	~~Log levels are arranged as follows:~~
	~~{\| class="wikitable" style="width: 700px;"~~
	\|-
	~~\| style="text-align: center;width: 120px;"\|Lowest Level \|\|'''CRITICAL'''~~
	~~\| style="width: 500px;"\|Indicates something very important that should always be logged.~~
	\|-
	~~\| \|\| style="text-align: center;"\|'''ERROR'''~~
	~~\| Describes errors that occur during a program's operation.~~
	\|-
	~~\| \|\| style="text-align: center;"\|'''WARNING'''~~
	~~\| Warnings about a program's behaviour.~~
	\|-
	~~\| \|\| style="text-align: center;"\|'''INFO'''~~
	~~\| Supplemental information about a program's status.~~
	\|-
	~~\| \|\| style="text-align: center;"\|'''DEBUG'''~~
	~~\| Extra information that is only useful for debugging purposes.~~
	\|-
	~~\| style="text-align: center;"\|Highest Level \|\| style="text-align: center;"\|'''VERBOSE'''~~
	~~\| More information than is useful for most applications except intensive debugging.~~
	\|}

	Setting the log level will filter log entries to only allow messages of that level and below to be added to the log. For example, if the log level was '''INFO''', then logs of level '''DEBUG''' and '''VERBOSE''' will be ignored, while all other logs would be stored.

	Log levels can be independently set for all sources using the variant of <code>setSourceLevel</code> for your language. This is useful for filtering out log messages from sources that would otherwise flood the log. It can also be used to show logs from sources that are hidden by default.

	~~===Timestamp===~~
	~~The time that the message was logged in local time, formatted as:~~

	~~<code>YYYY-MM-DDTHH:MM:SS</code>~~

	~~===Message===~~
	~~This is the message written to the log. It will contain the information intended to be logged.~~

	~~==Log Rotation==~~
	Log rotation is the automated process of archiving the current log file and starting a new one once the log becomes too large. Rotating log files is a method of keeping file size down while still keeping track of all the latest log information.

	Log rotation is enabled by default in Phidget22, and will keep two files: the current log file and the latest archived log file. The maximum size and number of archived log files can be adjusted using the <code>setRotating</code> function in your language of choice.

	~~Archived log files will have a timestamp of the time they were archived appended to the end of the log filename, as follows:~~

	~~<code>log.txt.2018-01-05T10_47_16</code>~~

Patrick at 22:55, 31 January 2018

2018-01-31T22:55:42Z

← Older revision		Revision as of 22:55, 31 January 2018
Line 43:		Line 43:
	\| '''Internal Use''' Channel Matching Logs		\| '''Internal Use''' Channel Matching Logs
	\|-		\|-
	\| ~~_phidget22netctl~~		\| phidget22netctl
	\| ~~'''Internal Use'''~~ Network Control Logs		\| Network Control Logs
	\|-		\|-
	\| ~~_phidget22usb~~		\| phidget22usb
	\| USB Processing Logs		\| USB Processing Logs
	\|-		\|-

Jdecoux: /* Getting Started */

2018-01-22T20:58:06Z

Getting Started

← Older revision		Revision as of 20:58, 22 January 2018
Line 12:		Line 12:
	Simply <code>enable</code> logging with log level <code>INFO</code>, and use <code>log</code> to write your own messages to the log file.		Simply <code>enable</code> logging with log level <code>INFO</code>, and use <code>log</code> to write your own messages to the log file.

	~~<!--~~ This usage is covered in the ~~[[Phidget Logging Example]]~~, available for the core languages. ~~-->~~		This usage is covered in the Log examples, available for the core languages.

	==Anatomy of a Log==		==Anatomy of a Log==

Jdecoux: /* Getting Started */

2018-01-17T16:18:41Z

Getting Started

← Older revision		Revision as of 16:18, 17 January 2018
Line 12:		Line 12:
	Simply <code>enable</code> logging with log level <code>INFO</code>, and use <code>log</code> to write your own messages to the log file.		Simply <code>enable</code> logging with log level <code>INFO</code>, and use <code>log</code> to write your own messages to the log file.

	This usage is covered in the [[Phidget Logging Example]], available for the core languages.		<!-- This usage is covered in the [[Phidget Logging Example]], available for the core languages. -->

	==Anatomy of a Log==		==Anatomy of a Log==

Jdecoux: Created page with "Category:Logging TOC ==Logging== Logging is a set of functionality designed to quietly track the operation of a software program to be stored for later examination...."

2018-01-17T16:11:37Z

Created page with "Category:Logging __TOC__ ==Logging== Logging is a set of functionality designed to quietly track the operation of a software program to be stored for later examination...."

New page

[[Category:Logging]]
__TOC__

==Logging==

Logging is a set of functionality designed to quietly track the operation of a software program to be stored for later examination. It is generally used for debugging purposes.

==Getting Started==

For basic use of the log class, the only functions you need to worry about are <code>enable</code> and <code>log</code>.

Simply <code>enable</code> logging with log level <code>INFO</code>, and use <code>log</code> to write your own messages to the log file.

This usage is covered in the [[Phidget Logging Example]], available for the core languages.

==Anatomy of a Log==

To better understand the concepts in this guide, we will dissect a log entry to clarify its component parts.

[[Image:Log_Anatomy.png|link=|center]]

===Source===
Sources are a property of Phidgets Log messages that indicate where the log message originated. By default, the writing to the log using the <code>log</code> function of your language will write to the source named '''phidget22'''.

For more advanced applications, some log functions will allow you to specify custom sources to allow for specialized logging implementations.

====Hidden Sources====
In addition to the default phidget22 source, there are a number of background log sources that are hidden by default. This is to keep log files relatively clean and allow focus on messages that matter to the application.

These sources are:
{| class="wikitable" style="width: 700px;"
|-
| _phidget22bridge
| '''Internal Use''' Phidget Bridge Logs (Not the physical device)
|-
| _phidget22channel
| '''Internal Use''' Channel Information Logs
|-
| _phidget22disp
| '''Internal Use''' Phidget Dispatch Logs
|-
| _phidget22match
| '''Internal Use''' Channel Matching Logs
|-
| _phidget22netctl
| '''Internal Use''' Network Control Logs
|-
| _phidget22usb
| USB Processing Logs
|-
| phidget22net
| Network Logs
|}

===Log Level===
Log levels are designed to sort messages in terms of importance, with lower log levels being generally the most important, and higher log levels carrying supplemental information.

Log levels are arranged as follows:
{| class="wikitable" style="width: 700px;"
|-
| style="text-align: center;width: 120px;"|Lowest Level ||'''CRITICAL'''
| style="width: 500px;"|Indicates something very important that should always be logged.
|-
| || style="text-align: center;"|'''ERROR'''
| Describes errors that occur during a program's operation.
|-
| || style="text-align: center;"|'''WARNING'''
| Warnings about a program's behaviour.
|-
| || style="text-align: center;"|'''INFO'''
| Supplemental information about a program's status.
|-
| || style="text-align: center;"|'''DEBUG'''
| Extra information that is only useful for debugging purposes.
|-
| style="text-align: center;"|Highest Level || style="text-align: center;"|'''VERBOSE'''
| More information than is useful for most applications except intensive debugging.
|}

Setting the log level will filter log entries to only allow messages of that level and below to be added to the log. For example, if the log level was '''INFO''', then logs of level '''DEBUG''' and '''VERBOSE''' will be ignored, while all other logs would be stored.

Log levels can be independently set for all sources using the variant of <code>setSourceLevel</code> for your language. This is useful for filtering out log messages from sources that would otherwise flood the log. It can also be used to show logs from sources that are hidden by default.

===Timestamp===
The time that the message was logged in local time, formatted as:

<code>YYYY-MM-DDTHH:MM:SS</code>

===Message===
This is the message written to the log. It will contain the information intended to be logged.

==Log Rotation==
Log rotation is the automated process of archiving the current log file and starting a new one once the log becomes too large. Rotating log files is a method of keeping file size down while still keeping track of all the latest log information.

Log rotation is enabled by default in Phidget22, and will keep two files: the current log file and the latest archived log file. The maximum size and number of archived log files can be adjusted using the <code>setRotating</code> function in your language of choice.

Archived log files will have a timestamp of the time they were archived appended to the end of the log filename, as follows:

<code>log.txt.2018-01-05T10_47_16</code>

Logging Explained - Revision history

Mparadis: Redirected page to Phidget Logging

Patrick at 22:55, 31 January 2018

Jdecoux: /* Getting Started */

Jdecoux: /* Getting Started */

Jdecoux: Created page with "Category:Logging __TOC__ ==Logging== Logging is a set of functionality designed to quietly track the operation of a software program to be stored for later examination...."

Jdecoux: Created page with "Category:Logging TOC ==Logging== Logging is a set of functionality designed to quietly track the operation of a software program to be stored for later examination...."