Server Metrics Appendix
Server Metrics Appendix
29.1 About the Server Metrics Appendix
In this appendix unless otherwise stated, the term server refers to an SAP BusinessObjects server, and not to the machine that SAP BusinessObjects Business Intelligence platform is installed or running on.
Server metrics are not available on servers that are not running.
Related Topics
•
Analyzing server metrics
29.1.1 Common Server Metrics
The following metrics describe the machine that the specified server is running on.
Table 29-1: Machine-specific metrics
Metric
Machine Name
Operating System
CPU Type
Description
The host name of the machine that the server is running on.
The operating system of the machine that the server is running on.
The type of Central Processing Units of the machine that the server is running on. This metric is not available on Adaptive Processing Servers or Web Application Container Servers (WACS).
935 2012-12-12
Server Metrics Appendix
Metric
CPUs
RAM (MB)
Local Time
Disk Size (GB)
Used Disk Space (GB)
Description
The number of CPUs that are available to the server.
On multi-core hardware, this metric may report the number of logical CPUs, and not the number of physical processors. This metric is not available on Adaptive Processing Servers or Web Application Container
Servers (WACS).
The amount of memory in megabytes that is available on the machine that the server is running on. This metric is not available on Adaptive Processing Servers or Web Application Container Servers (WACS).
The local time.
The size of the disk that SAP BusinessObjects Business Intelligence platform is installed on, in gigabytes.
This metric is not available on Adaptive Processing
Servers or Web Application Container Servers
(WACS).
The amount of used space on the disk, in gigabytes, that SAP BusinessObjects Business Intelligence platform is installed on. This includes disk space that is used by other programs on the machine, and not just space used by SAP BusinessObjects Business Intelligence platform. This metric is not available on Adaptive Processing Servers or Web Application Container
Servers (WACS).
The following metrics describe the specified SAP BusinessObjects server.
Table 29-2: Server-specific metrics
Metric
Name Server
Registered Name
Version
Start Time
Description
The name and port number of the CMS server that this server publishes its address to.
The internal name of the server. This is not the name that appears on the "Servers" screen of the CMC.
The version of the server.
The time that the server was most recently started.
936 2012-12-12
Server Metrics Appendix
Metric
PID
Host Name
Host IP Address
Request Port
Busy Server Threads
Description
The unique Process ID number for the server. The operating system of the machine that the server is running on generates the PID. The PID can be used to identify the specific server.
A comma-separated list of host names that are currently being used by the server.
A comma-separated list of IP Addresses that the server listens for requests on.
The port from which the server receives requests from other servers. If the server is listening to requests on more than one IP Address, the request port for the server will always be the same. If any other process uses this request port, the server will not start. Ensure that other processes do not use this port.
The number of server threads that are currently servicing a request. If this number is the same as the maximum thread pool size of the server, it indicates that the system can't process additional requests in parallel and that new requests may have to wait for busy threads to become available.
Table 29-3: Auditing Metrics
Metric
Current Number of Auditing Events in the Queue
Description
The number of auditing events that an Auditee has recorded, but which have not yet been retrieved by the CMS Auditor. If this number increases without bound, it could indicate that Auditing is not configured correctly or that the system is heavily loaded and generating audit events faster than the Auditor can retrieve them.
Note:
When stopping a server, first disable it and wait for this metric to reach “0”. Otherwise you may have auditing events that remain in the queue and do not reach the Auditing Data Store until the server is restarted and the CMS polls for them.
937 2012-12-12
