There are different session types that are defined in the system. The following table shows how KPIs count these sessions:
Note: All predefined KPIs are installed as Inactive. For a KPI to begin functioning in your system, it must be set to Active. Navigate to Service Desk, KPIs on the Administration tab and search for the inactive KPI. Open the KPI and click Activate.
Important! Multiple versions of a KPI with the same name cannot be active at the same time.
|
Session Type |
Session Type Description |
Counted by KPIs |
|
Web Client |
Web browser session |
|
|
Java Client |
Java client session |
|
|
Web Services |
SOAP Web services session |
|
|
Utility |
Server utility session |
|
|
Portal |
Portal session |
|
|
Knowledge Chat |
Knowledge Chat session |
|
|
Mail Server |
Mail Server session |
|
|
Custom Application |
Custom Application session |
|
|
PDA Client |
PDA Client session |
|
|
REST Client |
REST Web Services Session |
|
Example: KPIs calculating user counts
One licensed (that have the Licensed? check box selected) and two unlicensed end users are logged into the web self-service interface and reviewing some announcements.
At the same time five licensed analysts (that have the Licensed? check box selected) are logged into the analyst interface and working on incidents. One of the analysts also logs in to the SOAP Web Services interface.
(Applicable for advanced availability configuration only) Example: KPIs calculating user counts from different nodes
A licensed analyst logs in to the analyst interface from the background server and works on incidents. The same analyst logs in to the analyst interface from the application server. The webConcurrentLicenseCt KPI shows a count of one, meaning that one license is currently being used, irrespective of the number of nodes or servers the user has logged in from.
|
Copyright © 2013 CA.
All rights reserved.
|
|