From Bright Pattern Documentation
< 3.17:Reporting-database-specification
Revision as of 21:39, 5 June 2017 by Tracy (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
• 3.10 • 3.11 • 3.12 • 3.13 • 3.14 • 3.15 • 3.16 • 3.17 • 3.18

concurrent_users

The concurrent_users table tracks the number of users that were using the system at any moment in the past. A new row is added every time when a number of logged in users changes from a non-zero value (i.e., when a non-first user logs in or any user logs out), but not more frequently than once a minute. (After a first login/logout within a given minute, all subsequent logins/logouts that happen within that same minute will be aggregated and written as a single record one minute after.) A new record is also created unconditionally at the configured Reset time for daily statistics.


Description of Data

The following table offers the name (i.e., ID), data type (e.g., BIGINT, BINARY, BIT, DATETIME, ENUM, INT, VARCHAR, etc.), and description for each metric (i.e., column) of the concurrent_users table.


Column Name Data Type Description
num_users INT Number of users that were logged into the system in the interval specified by start_time and end_time
users JSON array This is a list of usernames of users that were logged into the system in the interval specified by start_time and end_time.

Users are specified as JSON array of [username1, username2, … usernameN] where N = num_users.

start_time TIMESTAMP Start time of the interval for which the num_users and users data in this record remains valid.

Time is given in the Universal Coordinated Time (UTC) time zone, and the time is rounded to a minute.

Note that it is normal for this time to differ by a few seconds from the time of state changes reported in the agent_activity table.

end_time TIMESTAMP End time of the interval for which the num_users and users data in this record remains valid.

Time is given in the Universal Coordinated Time (UTC) time zone, and the time is rounded to a minute.

Note that it is normal for this time to differ by a few seconds from the time of state changes reported in the agent_activity table.


< Previous | Next >