AppSuite:Logincounter - Revision history

Ioannis.chouklis at 11:05, 9 July 2018

2018-07-09T11:05:54Z

@@ Line 1: / Line 1: @@
 = Login Counter =
-Whenever a user is logged in through the login servlet, the context id, user id, client identification string and a time stamp is saved to the database. If a database entry for this combination of context, user and client is already present, only the timestamp is updated. This means that the database holds the information for the '''last''' login of a specific user with a specific client. This data can be retrieved again with the <code>logincounter</code> tool to show how many users logged in through which client(s) in a given timeframe.
+The content on this page has moved to https://documentation.open-xchange.com/7.10.0/middleware/components/commandlinetools/logincounter.html.
-Please note that only '''logins''' are counted. Depending on the server configuration and the client, sessions may be reused when a user re-accesses the system even after a few hours or days. In this case the login timestamp is not updated. This means that <tt>logincounter</tt> does not necessarily show the number of active users, especially if the request only covers a short timeframe.
+Note: Open-Xchange is in the process of migrating all its technical documentation to a new and improved documentation system (https://documentation.open-xchange.com). Please note as the migration takes place more information will be available on the new system and less on this system. Thank you for your understanding during this period of transition.

Sonja.krause-harder at 10:32, 21 July 2014

2014-07-21T10:32:10Z

← Older revision		Revision as of 10:32, 21 July 2014
Line 23:		Line 23:
	\|Connector 2 for Microsoft Outlook		\|Connector 2 for Microsoft Outlook
	\|<tt>USM-JSON</tt>		\|<tt>USM-JSON</tt>
			\|-
			\|OX Notifier
			\|<tt>OpenXchange.HTTPClient.OXNotifier</tt>
	\|-		\|-
	\|CardDAV		\|CardDAV

Sonja.krause-harder at 10:30, 21 July 2014

2014-07-21T10:30:34Z

← Older revision		Revision as of 10:30, 21 July 2014
Line 22:		Line 22:
	\|-		\|-
	\|Connector 2 for Microsoft Outlook		\|Connector 2 for Microsoft Outlook
	\|<tt>~~OpenXchange.HTTPClient.OXAddIn~~</tt>		\|<tt>USM-JSON</tt>
	\|-		\|-
	\|CardDAV		\|CardDAV

Sonja.krause-harder: /* Examples */

2014-07-18T09:06:42Z

Examples

← Older revision		Revision as of 09:06, 18 July 2014
Line 78:		Line 78:
	Restrict output to logins through any OX Drive client:		Restrict output to logins through any OX Drive client:

	$ /opt/open-xchange/sbin/logincounter -s "2014-06-01 00:00:00" -e "2014-06-30 23:59:59" -r ".OXDrive."		$ /opt/open-xchange/sbin/logincounter -s "2014-06-01 00:00:00" -e "2014-06-30 23:59:59" -r ".*OXDrive"

	Same as above, but remove duplicates in the total count (i.e. users using OX Drive on two platforms are only counted once):		Same as above, but remove duplicates in the total count (i.e. users using OX Drive on two platforms are only counted once):

	$ /opt/open-xchange/sbin/logincounter -s "2014-06-01 00:00:00" -e "2014-06-30 23:59:59" -r ".OXDrive." -a		$ /opt/open-xchange/sbin/logincounter -s "2014-06-01 00:00:00" -e "2014-06-30 23:59:59" -r ".*OXDrive" -a

	Show all logins through the App Suite Web UI:		Show all logins through the App Suite Web UI:

Sonja.krause-harder: /* Login Counter */

2014-07-18T09:05:06Z

← Older revision		Revision as of 09:05, 18 July 2014
Line 3:		Line 3:
	Whenever a user is logged in through the login servlet, the context id, user id, client identification string and a time stamp is saved to the database. If a database entry for this combination of context, user and client is already present, only the timestamp is updated. This means that the database holds the information for the '''last''' login of a specific user with a specific client. This data can be retrieved again with the <code>logincounter</code> tool to show how many users logged in through which client(s) in a given timeframe.		Whenever a user is logged in through the login servlet, the context id, user id, client identification string and a time stamp is saved to the database. If a database entry for this combination of context, user and client is already present, only the timestamp is updated. This means that the database holds the information for the '''last''' login of a specific user with a specific client. This data can be retrieved again with the <code>logincounter</code> tool to show how many users logged in through which client(s) in a given timeframe.

	Please note~~: Only~~ logins are counted. Depending on the server configuration and the client, sessions may be reused when a user re-accesses the system even after a few hours or days. In this case the login timestamp is not updated. This means that <tt>logincounter</tt> does not necessarily show the number of active users, especially if the request only covers a short timeframe.		Please note that only '''logins''' are counted. Depending on the server configuration and the client, sessions may be reused when a user re-accesses the system even after a few hours or days. In this case the login timestamp is not updated. This means that <tt>logincounter</tt> does not necessarily show the number of active users, especially if the request only covers a short timeframe.

	The clients provided by Open-Xchange use the following client identification strings:		The clients provided by Open-Xchange use the following client identification strings:

Sonja.krause-harder at 09:04, 18 July 2014

2014-07-18T09:04:38Z

← Older revision		Revision as of 09:04, 18 July 2014
Line 1:		Line 1:
	= Login Counter =		= Login Counter =

	Whenever a user is logged in through the login servlet, the context id, user id, client identification string and a time stamp is saved to the database. If a database entry for this combination of context, user and client is already present, only the timestamp is updated. This means that the database holds the information for the '''last''' login of a specific user with a specific client. This data can be ~~displayed~~ with the <code>logincounter</code> tool.		Whenever a user is logged in through the login servlet, the context id, user id, client identification string and a time stamp is saved to the database. If a database entry for this combination of context, user and client is already present, only the timestamp is updated. This means that the database holds the information for the '''last''' login of a specific user with a specific client. This data can be retrieved again with the <code>logincounter</code> tool to show how many users logged in through which client(s) in a given timeframe.

	Only logins are counted. Depending on the server configuration and the client, sessions may be reused when a user re-accesses the system even after a few hours or days. In this case the login timestamp is not updated. This means that <tt>logincounter</tt> does not necessarily show the number of active users, especially if the request only covers a short timeframe.		Please note: Only logins are counted. Depending on the server configuration and the client, sessions may be reused when a user re-accesses the system even after a few hours or days. In this case the login timestamp is not updated. This means that <tt>logincounter</tt> does not necessarily show the number of active users, especially if the request only covers a short timeframe.

	The clients provided by Open-Xchange use the following client identification strings:		The clients provided by Open-Xchange use the following client identification strings:

Sonja.krause-harder at 08:28, 18 July 2014

2014-07-18T08:28:17Z

← Older revision		Revision as of 08:28, 18 July 2014
Line 67:		Line 67:

	== Examples ==		== Examples ==

			Show all logins in the month of June 2014 by clients:

			$ /opt/open-xchange/sbin/logincounter -s "2014-06-01 00:00:00" -e "2014-06-30 23:59:59"

			Show all logins in the month of June 2014, but remove duplicate logins from the "Total" count. (This means a user who logged in with two different clients is only counted once in the total count.)

			$ /opt/open-xchange/sbin/logincounter -s "2014-06-01 00:00:00" -e "2014-06-30 23:59:59" -a

			Restrict output to logins through any OX Drive client:

			$ /opt/open-xchange/sbin/logincounter -s "2014-06-01 00:00:00" -e "2014-06-30 23:59:59" -r ".OXDrive."

			Same as above, but remove duplicates in the total count (i.e. users using OX Drive on two platforms are only counted once):

			$ /opt/open-xchange/sbin/logincounter -s "2014-06-01 00:00:00" -e "2014-06-30 23:59:59" -r ".OXDrive." -a

			Show all logins through the App Suite Web UI:

			$ logincounter -s "2014-06-01 00:00:00" -e "2014-06-30 23:59:59" -r "open-xchange-appsuite"

			Show all logins through either the App Suite or the Open-Xchange Server 6 Web UI:

			$ logincounter -s "2014-06-01 00:00:00" -e "2014-06-30 23:59:59" -r "(open-xchange-appsuite\|com.openexchange.ox.gui.dhtml)"

Sonja.krause-harder at 11:28, 17 July 2014

2014-07-17T11:28:02Z

← Older revision		Revision as of 11:28, 17 July 2014
Line 3:		Line 3:
	Whenever a user is logged in through the login servlet, the context id, user id, client identification string and a time stamp is saved to the database. If a database entry for this combination of context, user and client is already present, only the timestamp is updated. This means that the database holds the information for the '''last''' login of a specific user with a specific client. This data can be displayed with the <code>logincounter</code> tool.		Whenever a user is logged in through the login servlet, the context id, user id, client identification string and a time stamp is saved to the database. If a database entry for this combination of context, user and client is already present, only the timestamp is updated. This means that the database holds the information for the '''last''' login of a specific user with a specific client. This data can be displayed with the <code>logincounter</code> tool.

	Only logins are counted. Depending on the server configuration and the client, sessions may be reused when a user re-accesses the system even after a few hours or days. In this case the login timestamp is not updated. This means that <tt>logincounter</tt> does not necessarily show the number of active users.		Only logins are counted. Depending on the server configuration and the client, sessions may be reused when a user re-accesses the system even after a few hours or days. In this case the login timestamp is not updated. This means that <tt>logincounter</tt> does not necessarily show the number of active users, especially if the request only covers a short timeframe.

	The clients provided by Open-Xchange use the following client identification strings:		The clients provided by Open-Xchange use the following client identification strings:

Sonja.krause-harder at 11:26, 17 July 2014

2014-07-17T11:26:18Z

← Older revision		Revision as of 11:26, 17 July 2014
Line 5:		Line 5:
	Only logins are counted. Depending on the server configuration and the client, sessions may be reused when a user re-accesses the system even after a few hours or days. In this case the login timestamp is not updated. This means that <tt>logincounter</tt> does not necessarily show the number of active users.		Only logins are counted. Depending on the server configuration and the client, sessions may be reused when a user re-accesses the system even after a few hours or days. In this case the login timestamp is not updated. This means that <tt>logincounter</tt> does not necessarily show the number of active users.

	The clients provided by Open-Xchange use the following client identification strings ~~(this list is not yet complete)~~:		The clients provided by Open-Xchange use the following client identification strings:

	{\|		{\|

Sonja.krause-harder at 11:07, 17 July 2014

2014-07-17T11:07:03Z

← Older revision		Revision as of 11:07, 17 July 2014
Line 34:		Line 34:
	\|-		\|-
	\|OX Drive (native iOS client)		\|OX Drive (native iOS client)
	\|OpenXchange.iosClient.OXDrive		\|<tt>OpenXchange.iosClient.OXDrive</tt>
	\|-		\|-
	\|OX Drive (native Android client)		\|OX Drive (native Android client)
	\|OpenXchange.Android.OXDrive		\|<tt>OpenXchange.Android.OXDrive</tt>
	\|-		\|-
	\|OX Drive (native Mac OS X client)		\|OX Drive (native Mac OS X client)
	\|OSX.OXDrive		\|<tt>OSX.OXDrive</tt>
	\|-		\|-
	\|OX Drive (native Windows client)		\|OX Drive (native Windows client)
	\|OpenXchange.HTTPClient.OXDrive		\|<tt>OpenXchange.HTTPClient.OXDrive</tt>
	\|}		\|}