AppSuite:OX Logging - Revision history

Ioannis.chouklis: /* Examples */

2018-09-20T10:15:26Z

Examples

← Older revision		Revision as of 10:15, 20 September 2018
Line 365:		Line 365:
	Suppress category CONFIGURATION and CONNECTIVITY		Suppress category CONFIGURATION and CONNECTIVITY

	<code># logconf -oec CONFIGURATION CONNECTIVITY</code>		<code># logconf -oec CONFIGURATION CONNECTIVITY -A oxadminmaster -P secret</code>

	<code>		<code>

2018-09-20T10:15:14Z

Examples

← Older revision		Revision as of 10:15, 20 September 2018
Line 341:		Line 341:
	Create a user/context filter for user 1618, context 314 and loggers c.o.mail and c.o.appsuite with levels TRACE and DEBUG respectively		Create a user/context filter for user 1618, context 314 and loggers c.o.mail and c.o.appsuite with levels TRACE and DEBUG respectively

	<code># logconf -u 1618 -c 314 -a -l com.openexchange.appsuite=DEBUG com.openexchange.mail=TRACE</code>		<code># logconf -u 1618 -c 314 -a -l com.openexchange.appsuite=DEBUG com.openexchange.mail=TRACE -A oxadminmaster -P secret</code>

	<code>		<code>
Line 349:		Line 349:
	Remove a logger from a user/context filter with user 1618 and context 314		Remove a logger from a user/context filter with user 1618 and context 314

	<code># logconf -u 1618 -c 314 -d -l com.openexchange.appsuite</code>		<code># logconf -u 1618 -c 314 -d -l com.openexchange.appsuite -A oxadminmaster -P secret</code>

	<code>		<code>
Line 357:		Line 357:
	Change the log level for the com.openexchange.appsuite logger		Change the log level for the com.openexchange.appsuite logger

	<code># logconf -l com.openexchange.appsuite=DEBUG com.openexchange.usm=DEBUG</code>		<code># logconf -l com.openexchange.appsuite=DEBUG com.openexchange.usm=DEBUG -A oxadminmaster -P secret</code>

	<code>		<code>

2018-09-20T10:14:34Z

Syntax

← Older revision		Revision as of 10:14, 20 September 2018
Line 201:		Line 201:
	=== Syntax ===		=== Syntax ===
	<code>		<code>
	logconf [[-a \| -d] [-c <contextid> [-u <userid>] \| -e <sessionid>] [-l <logger_name>=<logger_level> ...] -A <masterAdmin> -P <masterAdminPassword> [-p <RMI-Port>] [-s <RMI-Server]] \| [-oec <category_1>,...] \| [-cf] \| [-lf] \| [-ll [<logger_1> ...] \| [dynamic]] \| [-le] \| [-h]		logconf [-a \| -d] [-c <contextid> [-u <userid>] \| -e <sessionid>] [-l <logger_name>=<logger_level> ...] -A <masterAdmin> -P <masterAdminPassword> [-p <RMI-Port>] [-s <RMI-Server] \| [-oec <category_1>,...] \| [-cf] \| [-lf] \| [-ll [<logger_1> ...] \| [dynamic]] \| [-le] \| [-h]
	</code>		</code>

2018-09-20T10:14:05Z

Syntax

← Older revision		Revision as of 10:14, 20 September 2018
Line 201:		Line 201:
	=== Syntax ===		=== Syntax ===
	<code>		<code>
	logconf [[-a \| -d] [-c <contextid> [-u <userid>] \| -s <sessionid>] [-l <logger_name>=<logger_level> ...] -A <masterAdmin> -P <masterAdminPassword> [-p <RMI-Port>] [-s <RMI-Server]] \| [-oec <category_1>,...] \| [-cf] \| [-lf] \| [-ll [<logger_1> ...] \| [dynamic]] \| [-le] \| [-h]		logconf [[-a \| -d] [-c <contextid> [-u <userid>] \| -e <sessionid>] [-l <logger_name>=<logger_level> ...] -A <masterAdmin> -P <masterAdminPassword> [-p <RMI-Port>] [-s <RMI-Server]] \| [-oec <category_1>,...] \| [-cf] \| [-lf] \| [-ll [<logger_1> ...] \| [dynamic]] \| [-le] \| [-h]
	</code>		</code>

2018-09-20T10:11:39Z

Parameters

← Older revision		Revision as of 10:11, 20 September 2018
Line 234:		Line 234:
	\| The user id for which to create the log filter		\| The user id for which to create the log filter
	\|-		\|-
	\| -s,--session <sessionid>		\| -e,--session <sessionid>
	\| The session id for which to create the log filter		\| The session id for which to create the log filter
	\|-		\|-
Line 258:		Line 258:
	{\| border="1"		{\| border="1"
	\|-		\|-
	\| -U, --~~JMX-User~~ <username>		\| -A, --adminuser <username>
	\| ~~JMX~~ username		\| Master admin username
	\|-		\|-
	\| -P, --~~JMX-Password~~ <password>		\| -P, --adminpass <password>
	\| ~~JMX~~ password		\| Master admin password
	\|-		\|-
	\| -p, --~~JMX-Port~~ <~~port~~>		\| -s, --server <rmiServer>
	\| ~~JMX~~ port		\| Optional RMI server (Defaults to localhost)
			\|-
			\| -p, --port <rmiPort>
			\| Optional RMI port (Defaults to 1099)
	\|-		\|-
	\|}		\|}

2018-09-20T10:08:40Z

Syntax

← Older revision		Revision as of 10:08, 20 September 2018
Line 201:		Line 201:
	=== Syntax ===		=== Syntax ===
	<code>		<code>
	logconf [-a \| -d] [-c <contextid> [-u <userid>] \| -s <sessionid>] [-l <~~logger_name_1~~>=<~~logger_level_x~~> ...] [-U <~~JMX-User~~> -P <~~JMX-Password~~> [-p <~~JMX~~-Port>]]		logconf [[-a \| -d] [-c <contextid> [-u <userid>] \| -s <sessionid>] [-l <logger_name>=<logger_level> ...] -A <masterAdmin> -P <masterAdminPassword> [-p <RMI-Port>] [-s <RMI-Server]] \| [-oec <category_1>,...] \| [-cf] \| [-lf] \| [-ll [<logger_1> ...] \| [dynamic]] \| [-le] \| [-h]
	</code>		</code>

2017-09-09T06:51:38Z

Categories vs. Log Levels

← Older revision		Revision as of 06:51, 9 September 2017
Line 288:		Line 288:
	#: For this case only the -oec flag is relevant		#: For this case only the -oec flag is relevant

	=== Categories vs. Log Levels ===		=== Exception Categories vs. Log Levels ===

	The OX server defines different categories to the OX exceptions that are thrown during the operation. Those categories should not be confused with the logging levels <code>{OFF, ERROR, WARN, INFO, DEBUG, TRACE, ALL}</code> of the logback framework which are described [http://logback.qos.ch/manual/architecture.html#effectiveLevel here].		The OX server defines different categories to the OX exceptions that are thrown during the operation. Those categories should not be confused with the logging levels <code>{OFF, ERROR, WARN, INFO, DEBUG, TRACE, ALL}</code> of the logback framework which are described [http://logback.qos.ch/manual/architecture.html#effectiveLevel here].

2017-09-09T06:51:29Z

Logging Filters vs. Loggers

← Older revision		Revision as of 06:51, 9 September 2017
Line 274:		Line 274:
	TRUNCATED, CONFLICT, CAPACITY, WARNING}		TRUNCATED, CONFLICT, CAPACITY, WARNING}

	=== Logging Filters vs. Loggers ===		=== Logging Filters vs. Loggers vs. Exception Categories ===

	As already mentioned in the beginning, with this command line tool you can do multiple things, therefore there are different "categories" of data objects so to speak, i.e. Logging Filters, Loggers and Exception Categories. Hence, specific flags of the tool are explicitly used for only one of these data object categories and nowhere else (with the exception of the -l flag):		As already mentioned in the beginning, with this command line tool you can do multiple things, therefore there are different "categories" of data objects so to speak, i.e. Logging Filters, Loggers and Exception Categories. Hence, specific flags of the tool are explicitly used for only one of these data object categories and nowhere else (with the exception of the -l flag):

2017-09-09T06:50:05Z

logconf CLT

@@ Line 273: / Line 273: @@
 Valid categories: {ERROR, USER_INPUT, CONFIGURATION, PERMISSION_DENIED, TRY_AGAIN, CONNECTIVITY, SERVICE_DOWN,
 TRUNCATED, CONFLICT, CAPACITY, WARNING}
 === Categories vs. Log Levels ===

2016-11-02T14:01:22Z

Remote logging to logstash

← Older revision		Revision as of 14:01, 2 November 2016
Line 181:		Line 181:
	}		}

	And the following filter to your filter configuration (note that you will have to adjust your timezone):		And the following filter to your filter configuration (note that you will have to adjust your timezone). The ruby code block is only needed for Elasticsearch version 2.0 or newer.
	if [type] == "LogX" {		if [type] == "LogX" {
	json {		json {
Line 190:		Line 190:
	timezone => "Europe/Berlin"		timezone => "Europe/Berlin"
	remove_field => ["timestamp"]		remove_field => ["timestamp"]
			}
			ruby {
			code => "event.to_hash.keys.each { \|k\| event[ k.gsub('.','_') ] = event.remove(k) if k.include?'.' }"
	}		}
	}		}