From Bright Pattern Documentation
Jump to: navigation, search
(Marked this version for translation)
(Updated via BpClonePage extension. Source page: draft:Reporting-database-specification/concurrent users)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
<translate>= concurrent_users= <!--T:1-->
+
= 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 [[contact-center-administrator-guide/ReportingSettings|Reset time for daily statistics]].  
+
The ''concurrent_users'' table tracks the number of users that were using the system at any moment in the past. The table segments agents and mobile users from the total count by their privileges. A new entry is added to the table whenever there is a change in the number of logged-in users from a non-zero value. This occurs, for instance, when a new user logs in while another user is already logged in, or when any user logs out. However, these entries are not added 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 [[contact-center-administrator-guide/ReportingSettings|Reset time for daily statistics]].  
  
 +
== Description of Data ==
  
== Description of Data == <!--T:2-->
 
 
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.
 
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.
  
  
<!--T:3-->
 
 
{|border="1" style="border-collapse:collapse" cellpadding="5"
 
{|border="1" style="border-collapse:collapse" cellpadding="5"
 
|'''Column Name'''
 
|'''Column Name'''
Line 16: Line 15:
 
|INT
 
|INT
 
|Number of users that were logged into the system in the interval specified by ''start_time'' and ''end_time''
 
|Number of users that were logged into the system in the interval specified by ''start_time'' and ''end_time''
 +
|-
 +
|'''concurrent_agent_users'''
 +
|INT
 +
|Number of users who have ''Handle automatically distributed interactions'', ''Handle Email and Cases'', or ''Handle service chats'' privilege.
 +
|-
 +
|'''concurrent_mobile_users'''
 +
|INT
 +
|Number of users who have the ''Login to mobile user app'' privilege.
 +
|-
 +
|'''concurrent_agent_mobile_users'''
 +
|INT
 +
|The number of users who have both ''Login to mobile user app'' and ''Handle automatically distributed interactions'' privileges.
 
|-
 
|-
 
|'''users'''
 
|'''users'''
Line 21: Line 32:
 
|This is a list of usernames of users that were logged into the system in the interval specified by ''start_time'' and ''end_time''.
 
|This is a list of usernames of users that were logged into the system in the interval specified by ''start_time'' and ''end_time''.
  
<!--T:4-->
 
 
Users are specified as JSON array of ''[username1, username2, … usernameN]'' where ''N = num_users''.
 
Users are specified as JSON array of ''[username1, username2, … usernameN]'' where ''N = num_users''.
 
|-
 
|-
Line 28: Line 38:
 
|Start time of the interval for which the ''num_users'' and ''users'' data in this record remains valid.
 
|Start time of the interval for which the ''num_users'' and ''users'' data in this record remains valid.
  
<!--T:5-->
 
 
Time is given in Universal Coordinated Time (UTC), and the time is rounded to a minute.
 
Time is given in Universal Coordinated Time (UTC), and the time is rounded to a minute.
  
<!--T:6-->
 
 
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.
 
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.
 
|-
 
|-
Line 38: Line 46:
 
|End time of the interval for which the ''num_users'' and ''users'' data in this record remains valid.
 
|End time of the interval for which the ''num_users'' and ''users'' data in this record remains valid.
  
<!--T:7-->
 
 
Time is given in Universal Coordinated Time (UTC), and the time is rounded to a minute.
 
Time is given in Universal Coordinated Time (UTC), and the time is rounded to a minute.
  
<!--T:8-->
 
 
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.
 
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.
 
|}
 
|}
 
 
 
 
</translate>
 

Latest revision as of 08:50, 15 August 2024

• 日本語
• 5.19 • 5.2 • 5.3 • 5.8

concurrent_users

The concurrent_users table tracks the number of users that were using the system at any moment in the past. The table segments agents and mobile users from the total count by their privileges. A new entry is added to the table whenever there is a change in the number of logged-in users from a non-zero value. This occurs, for instance, when a new user logs in while another user is already logged in, or when any user logs out. However, these entries are not added 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
concurrent_agent_users INT Number of users who have Handle automatically distributed interactions, Handle Email and Cases, or Handle service chats privilege.
concurrent_mobile_users INT Number of users who have the Login to mobile user app privilege.
concurrent_agent_mobile_users INT The number of users who have both Login to mobile user app and Handle automatically distributed interactions privileges.
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 Universal Coordinated Time (UTC), 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 Universal Coordinated Time (UTC), 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 >