When the user clicks on the administrative User Sign On<\/strong> screen, the following report appears:<\/p>\n The length of time for which entries are kept in the log is dependent upon the behavior setting named SYSTEM_LOG_EXPIRE_TIME_DAYS. Large logs may take some time to download for the report. If allowed to grow with no constraints, the sign on log can grow to an enormous size, retaining information that may no longer have value. A behavior setting named SYSTEM_LOG_EXPIRE_TIME_DAYS controls how long information is retained in the log. The default for this time is 30 days, but can be changed by the administrator. An internal system task within ExtraView deletes sign on log messages older than this time each hour, to avoid a buildup of the task that would take a considerable amount of time.<\/p>\n Usage is straightforward. If you do not select any filters, the entire user sign on log will be produced. You may select a subset of the log using the date filters provided.<\/p>\n You can sort the report by any of the columns, by clicking on its title. An arrow shows the column currently used for the sort. Note that if you click on the column that is currently selected, the report is resorted, but in descending rather than ascending order.<\/p>\n The Concurrent Users<\/strong> column shows how many users were connected at the moment that the sign on took place, allowing you to monitor the number of users connected to ExtraView over time. This is an aid to capacity planning. Note that the report does not display counts for users who occupy a named user license. These users are not subject to any limitation as to when they can sign on and off.<\/p>\n The definitions of the columns in this report are:<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" The user sign on log allows the administrator to determine all sign on, sign off and unsuccessful accesses by users. When you access the sign on log, you are offered a choice of filters. The sign on log is accessed within Administration, Operational Tasks. This report may also be accessed through the Reports screen. The…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":23878,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_lmt_disableupdate":"no","_lmt_disable":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"class_list":["post-23894","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"\n![\"\"](\"\/v25\/extraview-media\/images\/ug\/querying_reporting\/admin-report-user-sign-on.png\")
<\/p>\n\n\n
\n \n\t\t\t\tColumn Name<\/td>\n \n\t\t\t\tDefinition<\/td>\n<\/tr>\n \n \n\t\t\t\tSign On\/Sign Off<\/td>\n \n\t\t\t\tSign on or sign off<\/td>\n<\/tr>\n \n \n\t\t\t\tTimestamp<\/td>\n \n\t\t\t\tDate and time of sign on\/sign off<\/td>\n<\/tr>\n \n \n\t\t\t\tResult<\/td>\n \n\t\t\t\tThis will display success or failure<\/td>\n<\/tr>\n \n \n\t\t\t\tFailure Reason<\/td>\n \n\t\t\t\tThis will show the reason the result was a failure<\/td>\n<\/tr>\n \n \n\t\t\t\tUser ID<\/td>\n \n\t\t\t\tUser ID entered<\/td>\n<\/tr>\n \n \n\t\t\t\tUser Name<\/td>\n \n\t\t\t\tThe name of the user<\/td>\n<\/tr>\n \n \n\t\t\t\tIP Address<\/td>\n \n\t\t\t\tAddress of sign on client<\/td>\n<\/tr>\n \n \n\t\t\t\tConcurrent Users<\/td>\n \n\t\t\t\tNumber of currently used concurrent licenses, not including the ADMIN or SYSTEM users if they are signed on. This is calculated as follows:<\/p>\n \n
\n \n\t\t\t\tGuest Users<\/td>\n \n\t\t\t\tThe number of user who are occupying guest licenses, signified by the role set in the behavior setting named DEFAULT_USER_ROLE<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n