--- sourceDocument: Australia Impact sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact Release : - australia ft:locale : - en-US ft:publication_title : - Australia Impact ft:clusterId : - ipact bundleId : - ipact --- # User information metrics # User information metrics {#ariaid-title1} * Release version: Australia * * Updated May 27, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read The metrics provide the user information performance snapshot within the ServiceNow AI Platform®. ## Session summary enduser {#io-user-info-metrics__section_kwl_kww_jjc} Sum of sessions that exist on each application node where at least one transaction has been executed; it's meant to be a gauge of real users. This includes sessions that are not logged in but have visited a page that is, login page. Application nodes can generally support large numbers that is, a few hundred of sessions. If one or more nodes shows evidence of extremely high session counts that is, approaching or over 1000, the application node may suffer performance degradation due to a variety of causes. Note: * If all application nodes show evidence of high session counts, review session timeouts to ensure that these are set to a reasonable value (i.e., 30 minutes with 90 minutes absolute maximum). If session timeouts are already reasonable, this may be an indication that additional application nodes should be added to the instance. * If one or more individual application nodes show unusually high session count, check whether other application nodes have recently restarted which may have caused active users to be 'moved' to remaining nodes causing a session imbalance. In this case, restart the node(s) with extremely high session count. {#io-user-info-metrics__ul_lwl_kww_jjc} ## Session summary loggedin {#io-user-info-metrics__section_wtl_kww_jjc} Sum of all active sessions that is, session objects in memory that exist on each application node for logged-in users. Application nodes can generally support large numbers that is, a few hundred of active sessions/session objects. If one or more nodes shows evidence of extremely high session counts that is, approaching or over 1000, the application node may suffer performance degradation due to a variety of causes. Note: * If all application nodes show evidence of high session counts, review session timeouts to ensure that these are set to a reasonable value that is, 30 minutes with 90 minutes absolute maximum. If session timeouts are already reasonable, this may be an indication that additional application nodes should be added to the instance. * If one or more individual application nodes show unusually high session count, check whether other application nodes have recently restarted which may have caused active users to be 'moved' to remaining nodes causing a session imbalance. In this case, restart the node(s) with extremely high session count. {#io-user-info-metrics__ul_xtl_kww_jjc} **Related reference** * [Anomaly insights](https://servicenow-prod.fluidtopics.net/4_QeeoMptTF3e9qrg4XWwg "The reference topic gives additional information for anomaly charts.") * [Feature availability based on package](https://servicenow-prod.fluidtopics.net/P9qjLGc3vCF_cOO3tzGPpA "The table outlines the access permissions for Performance Analytics features across production and sub production instances.") * [Auriga Intelligent Alert report](https://servicenow-prod.fluidtopics.net/nQSJ7KPMZhRA30JC0WUapA "Auriga Intelligent Alert is an advanced multivariate machine learning (ML) model that learns from historical issues on your instance to provide real-time insight. Auriga monitors your performance metrics to deliver notifications of noteworthy events or deviations from anticipated data patterns.") * [Transaction or response metrics](https://servicenow-prod.fluidtopics.net/zO1ipLkzD4Ui4sKzEQk4bg "The metrics provide a performance snapshot of classic UI transactions within the ServiceNow AI Platform.") * [Database performance metrics](https://servicenow-prod.fluidtopics.net/BR2AN_h8wOEd8ZtqZdLf4A "The metrics provide the database performance snapshot within the ServiceNow AI Platform.") * [Semaphores performance metrics](https://servicenow-prod.fluidtopics.net/Kk9mReT78mDBECtqFl7MWQ "The metrics provide the key performance indicators calculated at the instance level for the selected duration.") * [Event queues performance metrics](https://servicenow-prod.fluidtopics.net/gJEASVHBrJdFQHIBS8345w "The metrics provide the event performance snapshot within the ServiceNow AI Platform.") * [ECC Queue performance metrics](https://servicenow-prod.fluidtopics.net/RGxMtNOGgtVY6Q5itGNFaQ "The metrics provide the ECC Queue performance snapshot within the ServiceNow AI Platform.") * [Email performance metrics](https://servicenow-prod.fluidtopics.net/bogAIEvZQM6EVgHuNANWkw "The metrics provide the Email performance snapshot within the ServiceNow AI Platform.") * [Scheduler performance metrics](https://servicenow-prod.fluidtopics.net/mUgSGAMhziXWPxkMp4ZZJQ "The metrics provide the Schedulers performance snapshot within the ServiceNow AI Platform.") * [Job details performance metrics](https://servicenow-prod.fluidtopics.net/zU5pCERdUDwYINhrEtEmVw "The metrics provide the job details performance snapshot within the ServiceNow AI Platform.") * [Node health performance metrics](https://servicenow-prod.fluidtopics.net/Ym_5QZb7HaUEXusPO0FNVA "The metrics provide the node health performance snapshot within the ServiceNow AI Platform.") * [Host health performance metrics](https://servicenow-prod.fluidtopics.net/BPg~fi7mWtO2QDvoJtmlbw "The metrics provide the host health performance snapshot within the ServiceNow AI Platform.") * [Standby replication Lag](https://servicenow-prod.fluidtopics.net/~bnGXSPhIInh_QygPmu8lA "A read replica is a copy of the primary DB that reflects changes to the primary in almost real time, in normal circumstances. The lag represents the database server of the instance that is behind in seconds.") * [Pool Replication Lag](https://servicenow-prod.fluidtopics.net/GZt7jzZ4mbs0axGHLTG75w "Pool replication lag is the number of seconds that a Standby database or a read replica database lags behind the primary database.") * [Chat details performance metrics](https://servicenow-prod.fluidtopics.net/3ITlZgnjjx7hFU0jPdggHA "For the operations team to get the insights of current load across main components of AWA channel infrastructure like queues and agents, and to monitor load during events of chat spikes.") * [Cluster details performance metrics](https://servicenow-prod.fluidtopics.net/gCpPJvTx4G~JcYX9~VAIVA "The metrics provide the cluster details and Encryption status snapshot within the ServiceNow AI Platform.") * [Load balancer performance metrics](https://servicenow-prod.fluidtopics.net/U6~7lb0jujHirGTJlHHmZA "The metrics provide the load balancer performance snapshot within the ServiceNow AI Platform.") * [Instance Data Replication](https://servicenow-prod.fluidtopics.net/ScxZA~8x58vIrm57FTmurg "The Instance Data Replication (IDR) copies data updates from one instance, called the producer instance, to one or more other instances called the consumer instances.")