Replikwando Error Logging - Revision history

Jmckinstry: Added new log type and log level.

2014-11-25T01:19:50Z

Added new log type and log level.

← Older revision		Revision as of 20:19, 24 November 2014
Line 16:		Line 16:
	* GENERAL		* GENERAL
	* NOTIFY		* NOTIFY
			* DEBUG

	==Critical==		==Critical==
Line 56:		Line 57:
	* Function creation without determinism set		* Function creation without determinism set
	* Short-form queries being added to sqlite file		* Short-form queries being added to sqlite file

			==Debug==
			Contains tons of otherwise-useless output; queries being written out and such.

			Not good for general use.

			Examples:
			* First 2KB of each query being sent to remote server.

	=Log Types=		=Log Types=
Line 80:		Line 89:

	* EXTRA_DATA_SQLITE_CHANGE		* EXTRA_DATA_SQLITE_CHANGE
			* TEST_SUITE

	==General==		==General==
Line 113:		Line 123:
	==Extra_data_SQLite_Change==		==Extra_data_SQLite_Change==
	Notifications for SQLite values being manipulated. Performance logging.		Notifications for SQLite values being manipulated. Performance logging.

			==Test_Suite==
			Eventually will be used for parse-friendly output to enable testing. I hope.

	=Log Format=		=Log Format=

Jmckinstry: /* Log Format */

2014-09-04T22:13:29Z

Log Format

← Older revision		Revision as of 17:13, 4 September 2014
Line 115:		Line 115:

	=Log Format=		=Log Format=
			Currently, the log format is hard-coded to be:
			* Locale_String_Date_Time [Log_Level : Log_Type] - Full_Message

			Please note that Full_message may have any variety of formatting, including tabbing, unescaped raw ascii values, and line returns.

	=Known Errors=		=Known Errors=
	Please review [[Known Replikwando Errors\|this wiki page]].		Please review [[Known Replikwando Errors\|this wiki page]].

Jmckinstry at 22:10, 4 September 2014

2014-09-04T22:10:47Z

← Older revision		Revision as of 17:10, 4 September 2014
Line 81:		Line 81:
	* EXTRA_DATA_SQLITE_CHANGE		* EXTRA_DATA_SQLITE_CHANGE

	===General===		==General==
	Catch-all category for anything that comes from non-specific locations. It should probably always be enabled.		Catch-all category for anything that comes from non-specific locations. It should probably always be enabled.

	===Startup===		==Startup==
	Issues that occur while Replikwando is starting up and putting itself into a normal running state.		Issues that occur while Replikwando is starting up and putting itself into a normal running state.

	===Shutdown===		==Shutdown==
	Issues that occur while Replikwando is closing down and cleaning up values.		Issues that occur while Replikwando is closing down and cleaning up values.

	===Performance===		==Performance==
	Logged values related to performance, such as query lengths and queue sizes.		Logged values related to performance, such as query lengths and queue sizes.

	===Thread_Main===		==Thread_Main==
	Issues that occur in the main thread of Replikwando. The main thread doesn't do much, and most if not all values that go here would be better handled under General instead.		Issues that occur in the main thread of Replikwando. The main thread doesn't do much, and most if not all values that go here would be better handled under General instead.

	===Thread_Read===		==Thread_Read==
	Issues that occur during reading values from the local database.		Issues that occur during reading values from the local database.

	===Thread_Parse===		==Thread_Parse==
	Issues that occur during the parsing of unparsed queries. Involves tokenization and introspection of MySQL queries.		Issues that occur during the parsing of unparsed queries. Involves tokenization and introspection of MySQL queries.

	===Thread_Store===		==Thread_Store==
	Issues that occur during saving parsed queries to the SQLite database file.		Issues that occur during saving parsed queries to the SQLite database file.

	===Thread_Send===		==Thread_Send==
	Issues that occur during sending values to any number of remote databases.		Issues that occur during sending values to any number of remote databases.

	===Thread_Heartbeat===		==Thread_Heartbeat==
	Issues that occur during the triggering of heartbeats, or the reading and writing of Replikwando Messages.		Issues that occur during the triggering of heartbeats, or the reading and writing of Replikwando Messages.

	===Extra_data_SQLite_Change===		==Extra_data_SQLite_Change==
	Notifications for SQLite values being manipulated. Performance logging.		Notifications for SQLite values being manipulated. Performance logging.

Jmckinstry: /* Log Types */

2014-09-04T22:10:01Z

Log Types

← Older revision		Revision as of 17:10, 4 September 2014
Line 58:		Line 58:

	=Log Types=		=Log Types=
			This setting determines what sources of message are considered for logging. It is completely agnostic of severity.

			==Values==
			This value can be set in replication.ini, logging::log_types.

			Multiple values may be specified on this line, in the form of
			* log_types=<log_type_value>[ log_type_value...]

			Acceptable values are:
			* GENERAL
			* STARTUP
			* SHUTDOWN
			* PERFORMANCE

			* THREAD_MAIN
			* THREAD_READ
			* THREAD_PARSE
			* THREAD_STORE
			* THREAD_SEND
			* THREAD_HEARTBEAT

			* EXTRA_DATA_SQLITE_CHANGE

			===General===
			Catch-all category for anything that comes from non-specific locations. It should probably always be enabled.

			===Startup===
			Issues that occur while Replikwando is starting up and putting itself into a normal running state.

			===Shutdown===
			Issues that occur while Replikwando is closing down and cleaning up values.

			===Performance===
			Logged values related to performance, such as query lengths and queue sizes.

			===Thread_Main===
			Issues that occur in the main thread of Replikwando. The main thread doesn't do much, and most if not all values that go here would be better handled under General instead.

			===Thread_Read===
			Issues that occur during reading values from the local database.

			===Thread_Parse===
			Issues that occur during the parsing of unparsed queries. Involves tokenization and introspection of MySQL queries.

			===Thread_Store===
			Issues that occur during saving parsed queries to the SQLite database file.

			===Thread_Send===
			Issues that occur during sending values to any number of remote databases.

			===Thread_Heartbeat===
			Issues that occur during the triggering of heartbeats, or the reading and writing of Replikwando Messages.

			===Extra_data_SQLite_Change===
			Notifications for SQLite values being manipulated. Performance logging.

	=Log Format=		=Log Format=

Jmckinstry: /* Values */

2014-09-04T22:02:03Z

Values

← Older revision		Revision as of 17:02, 4 September 2014
Line 6:		Line 6:
	==Values==		==Values==
	This value can be set in replication.ini, logging::loglevel.		This value can be set in replication.ini, logging::loglevel.

			Only one value is accepted, in the form of:
			* loglevel=<log_level_value>

	Acceptable values are (in order of criticality):		Acceptable values are (in order of criticality):

Jmckinstry: /* Log Levels */

2014-09-04T22:00:14Z

Log Levels

← Older revision		Revision as of 17:00, 4 September 2014
Line 2:		Line 2:

	=Log Levels=		=Log Levels=
			This setting determines what severity of issue is logged. Each level includes all the ones of higher priority as well.

	==Values==		==Values==
	This value can be set in replication.ini, logging::loglevel.		This value can be set in replication.ini, logging::loglevel.

Jmckinstry: /* Log Levels */

2014-09-04T21:58:49Z

Log Levels

← Older revision		Revision as of 16:58, 4 September 2014
Line 2:		Line 2:

	=Log Levels=		=Log Levels=
			==Values==
			This value can be set in replication.ini, logging::loglevel.

			Acceptable values are (in order of criticality):
			* CRITICAL
			* ERROR
			* WARNING
			* GENERAL
			* NOTIFY

			==Critical==
			Notifies the user that there are issues that require immediate attention (whether by user or programmer), and that Replikwando cannot function normally until they are corrected.

			Examples:
			* Basic configuration is not set
			* Could not connect to local or remote database on startup
			* Binary logging is not enabled
			* Could not create or open sqlite file
			* Processing threads have died unexpectedly (programmer must correct)
			* CRT or other generic unhandled error or exception (programmer must handle)

			==Error==
			Notifies the user that issues are coming up that are stopping Replikwando from functioning correctly.

			Examples:
			* Loss of local or remote connection
			* Inability to trigger a heartbeat

			==Warning==
			Notifies the user that some issues are coming up, but Replikwando is capable of getting along without intervention.

			Examples:
			* Any query that errors out for known reasons like DUPLICATE KEY or ALREADY_EXISTS

			==General==
			Details important state changes (like repushing) and other things that are nice to know, but won't require action by the users.

			Examples:
			* Repush started
			* Repush finished

			==Notify==
			Details general state changes and higher-level debugging information.

			Examples:
			* Heartbeat message received
			* Discarded known duplicate query (ROLLBACK; ROLLBACK;)
			* Function creation without determinism set
			* Short-form queries being added to sqlite file

	=Log Types=		=Log Types=

Jmckinstry: Creating frame for what's going to go in here

2014-09-04T21:45:28Z

Creating frame for what's going to go in here

New page

Contained within this page are the inner workings of Replikwando's logging system as of version 1.7.0.

=Log Levels=

=Log Types=

=Log Format=

=Known Errors=
Please review [[Known Replikwando Errors|this wiki page]].