Symptom: Language

SAP Knowledge Base Article
1772632 - Explanation of Server Monitoring Metrics for SAP BusinessObjects Business Intelligence 4.0
Version 4 Validity: 29.04.2014 - active Language English
Symptom
Included in this article you will find an explanation of monitored events for SAP BusinessObjects Business Intelligence 4.0 servers
Environment
SAP BusinessObjects Business Intelligence Platform 4.0
Resolution
l Monitoring in SAP BusinessObjects Business Intelligence 4.0 is used to capture the runtime and historical metrics of the platform 4.0 servers
for reporting and notification
l The monitoring application helps system administrators to identify if a service is functioning normally and if the response times are as
expected.
l Monitoring provides key business metrics, the monitoring application provides better insight into SAP BusinessObjects Business Intelligence
platform 4.0.
l To assist in the identification of poorly functioning servers an administrator can create rules assigned to each server with specific metrics.
The rules are assigned as “Caution” and “Danger” rules, explained below:
Caution: Server is slightly overloaded, nearing peak values
Danger: Server resources are over used, may not take new requests or may not complete current request successfully
l Below you will find tables that describe the available metrics to assign to these “Caution” and “Danger” rules for each Business Intelligence
service/server.
METRICS AVAILABLE TO ALL SERVERS
METRIC DESCRIPTION
The unique Process ID number for the server. The operating system of the machine that the server is
PID
running on generates the PID. The PID can be used to identify the specific server.
Highlights the current status of the service:
l "0" - Indicates that the health of the metric is bad.

Health State
l "1" - Indicates that the health of the metric is deteriorating and needs immediate attention.
l "2" - Indicates that the health of the metric is good.
Server Enabled State Indicates whether a service is currently in an “Enabled” status

Server Running State Indicates whether a service is currently in an “Running” status
METRICS COMMON TO MULTIPLE SERVERS:
METRIC SERVERS DESCRIPTION

Adaptive Processing Server The number of processors that are available to the
Available Processors Java Virtual Machine (JVM) on which the server is
Web Application Container Server running.
Crystal Reports 2011 Processing Server The average time, in milliseconds, the server has
spent processing the last 500 requests that the server
Average Processing Time (msec) Crystal Reports Processing Server has received. If this number is consistently high and
growing, consider creating additional servers on
Dashboard Processing Server other computers.
Adaptive Job Server
Adaptive Processing Server
Central Management Server
Connection Server
Crystal Reports 2011 Processing Server
Crystal Reports 2011 Report Application

Server The number of server threads that are currently
servicing a request. If this number is the same as the
Crystal Reports Cache Server maximum thread pool size of the server, it indicates
Busy Server Threads
that the system can't process additional requests in
Crystal Reports Processing Server parallel and that new requests may have to wait for
busy threads to become available.
Dashboard Cache Server
Dashboard Processing Server
Event Server
File Repository Server (I&O)
Web Application Container Server
Web Intelligence Processing Server

The percentage of total CPU time used by the server
during the previous 15 minutes. For example, if a
single thread fully utilizes one CPU of a four-CPU
CPU Usage Percentage last 15 minutes
system, the utilization is 25%. All processors
Web Application Container Server allocated to the JVM are considered. A value of
greater than 70% may indicate a bottleneck.
The percentage of total CPU time used by the server
during the previous five minutes. For example, if a
single thread fully utilizes one CPU of a four-CPU
CPU Usage Percentage last 5 minutes
system, the utilization is 25%. All processors
Web Application Container Server allocated to the JVM are considered. A value of
greater than 80% may indicate a CPU bottleneck.
Adaptive Job Server
Connection Server

Server
The number of CPUs that are available to the server.
On multi-core hardware, this metric may report the
CPUs Crystal Reports Cache Server number of logical CPUs, and not the number of
physical processors.
Crystal Reports Processing Server Event
Server
Dashoardb Cache Server

Adaptive Job Server

The number of auditing events that an Auditee has
Crystal Reports 2011 Report Application recorded, but which have not yet been retrieved by
Server the CMS Auditor. If this number increases without
Current Number of Auditing Events in the
bound, it could indicate that Auditing is not configured
Queue
correctly or that the system is heavily loaded and
Crystal Reports Cache Server
generating audit events faster than the Auditor can
retrieve them.
Event Server

The total amount of data, in kilobytes, that have been
Data transferred Crystal Reports Processing Server
transferred to clients since the server was started.
Adaptive Job Server
Connection Server

Server
The size of the disk that SAP BusinessObjects
Crystal Reports Cache Server
Disk size (GB) Business Intelligence platform is installed on, in
gigabytes.
Crystal Reports Processing Server
Event Server

The amount of memory, in megabytes, that is
Free Memory
available to the JVM for allocating new objects.
The number of threads that are deadlocked. Any
value greater than 0 indicates threads that will not run
JVM Deadlocked Threads Counter
again. Initiate a Thread Dump to obtain more
Web Application Container Server information about the cause of the problem.
The number of synchronized objects that have
Adaptive Processing Server threads that are waiting for access. Any value
JVM Locked Contention Count consistently greater than 0 may indicate threads that
Web Application Container Server will not run again. Initiate a Thread Dump to obtain
more information about the cause of the problem.
The maximum number of concurrent child processes
Max Child Processes Crystal Reports Processing Server
that are allowed on the server.
The maximum amount of memory, in megabytes, that
Maximum Memory
the Java virtual machine will attempt to use.
The maximum time, in milliseconds, that the server
Crystal Reports Processing Server has spent processing one of the last 500 requests. If
Maximum Processing Time (msec) this number is consistently high and growing,
Dashboard Cache Server consider creating additional servers on other
computers.
The minimum time, in milliseconds, that the server
Crystal Reports Processing Server has spent processing one of the last 500 requests. If
Minimum Processing Time (msec) this number is consistently high and growing,
Dashboard Cache Server consider creating additional servers on other
computers.
The number of threads serving requests received by
Number of active threads
the server (asynchronismthreadpool).

The number of connections that are currently open
Number of Open Connections
between the server and clients.

The number of currently jobs that the server and its
Number of Open Jobs Crystal Reports Processing Server
child processes are currently processing.
Crystal Reports Processing Server The number of requests that are either waiting to be
processed or are being processed. If this number is
Number of Queued Requests
consistently high and growing, consider creating
additional servers on other computers.
The number of requests that the server was unable to
Number of Requests Failed Crystal Reports Processing Server
complete since the server started.

The total number of requests that the server has
Number of Requests Served
served since it started.

Percentages of stopped system while Garbage
Collection (GC) was running during the last 15
minutes. In this state all application code running on
top of the Java virtual machine is prevented from
executing while the virtual machine performs a critical
Percentage of stopped system during GC stage of garbage collection that requires exclusive
last 15 minutes access.
Generally, a low single-digit value should be the
normal behavior, even under load. A double-digit
value over time might indicate an issue of low
throughput and needs to be investigated.
Percentages of stopped system while Garbage
Collection (GC) was running during the last five
minutes. In this state all APS services are prevented
from executing while the virtual machine performs a
Adaptive Processing Server critical stage of garbage collection that requires
Percentage of stopped system during GC exclusive access.
last 5 minutes
Generally, a low single-digit value should be the
normal behavior, even under load. A double-digit
value over time might indicate an issue of low
throughput and needs to be investigated.
Adaptive Job Server
Connection Server

Server
Crystal Reports Cache Server The amount of memory in megabytes that is available
RAM (MB)
on the machine that the server is running on.
Event Server

The number of requests that the server failed to
Requests Failure Rate (%) Crystal Reports Processing Server process as a percentage of the last 500 requests that
the server has received.
The total number of threads in all thread pools of the
Threads in Transport Layer
transport layer.
Adaptive Processing Server The total amount of memory, in megabytes, in the
Total Memory Java virtual machine. This value may vary over time,
Web Application Container Server depending on the host environment.
Adaptive Processing Server The total number of shared transport layer threads.
Transport Layer Thread Pool Size These threads can be used by any of the hosted
Web Application Container Server services on the Adaptive Processing Server.
Adaptive Job Server
Connection Server

Server The amount of used space on the disk, in gigabytes,
that SAP BusinessObjects Business Intelligence
Crystal Reports cache platform is installed on. This includes disk space that
Used Disk Space (GB)
is used by other programs on the machine, and not
Crystal Reports Processing Server just space used by SAP BusinessObjects Business
Intelligence platform.
Event Server
METRICS SPECIFIC TO THE ADAPTIVE JOB SERVER:
METRIC NAME DESCRIPTION

The number of jobs that are currently running on the server. If this number is high, the server
Concurrent Jobs
is busy.
Failed Job Creations The number of jobs that failed on the server.
The maximum number of concurrent jobs that have run at the same time on the server. This
Peak Jobs
number never goes down until the server is restarted.
Received Job Requests The number of jobs that were supposed to have run on the server.
METRICS SPECIFIC TO THE ADAPTIVE PROCESSING SERVER:

The number of data sources that are being used to supply data to the connections that have not timed
Cube Count
out.
DataFederator. Total Bytes of Disk Used
The amount of disk currently used by the running queries (in bytes).
by Query a Execution
DataFederator.Number of Loaded
The total number of connectors loaded in the service.
Connectors
DataFederator.Number of Queries
The total number of running queries consuming memory.
Consuming Memory
DataFederator.Number of Queries in
The total number of running queries currently in analyze step.
Query Analyze Step
The total number of running queries currently in execution step.
Query Execution Step
The total number of running queries currently in optimization step.
Query Optimization Step
DataFederator.Number of Queries Using
The total number of running queries using disk.
Disk
DataFederator.Number of Queries
The total number of running queries currently waiting for execution.
Waiting for Resources
DataFederator.Number of Running
The total number of running queries (consuming memory or not).
Queries
DataFederator.Total Bytes of Memory
The amount of memory used for caching metadata, statistics and connectors configuration (in bytes).
Used by Metadata Cache
DataFederator.Total Bytes of Memory
The amount of memory currently used by the running queries (in bytes).
Used by Query Execution
DataFederator.Total Bytes Produced by
The amount of data produced as output of queries (in bytes).
Query Execution
DataFederator.Total Bytes Transferred
The amount of data read from the data sources (in bytes).
from Data Sources
Number of Active Connections to Loaded
The total number of active connections to connectors loaded in the service.
Connectors
Number of Auditing Events Received
The total number of auditing events that have been recorded by the server since its start.
Since Server Startup
Number of Connections The total number of user connections to data federation query engine.
Number of Failed GCs The number of failed Garbage Collections since the server has started
Number of Failed Queries The total number of failed queries (exception raised).
The number of full Garbage Collections since the server has started. A rapid increase in this value
Number of Full GCs
may indicate a system under low memory conditions.
The number of page faults that have occurred while Garbage Collections were running during the last
Number of Page Faults during GC last 15
15 minutes. Any value greater than 0 indicates a system under heavy load and low memory
minutes
conditions.
The number of page faults that have occurred while Garbage Collections were running during the
Number of Page Faults during GC last 5
previous five minutes. Any value greater than 0 indicates a system under heavy load and low memory
minutes
conditions.
Query Count The number of data requests that are open between MDS clients and the server.
Session Count The current number of connections from MDAS clients to the server.

METRICS SPECIFIC TO THE CENTRAL MANAGEMENT SERVER (CMS):

The most recent date and time that the CMS successfully started to retrieve events from an
auditee. If the CMS is an auditor, this metric must show a time that is close to the time that
Auditing Database Last Updated On
the “Metrics” screen is loaded If this value is more than two hours prior to the time that the
screen is loaded, it may indicate that auditing is not working properly.
The duration of the last polling cycle in seconds. This indicates the maximum delay for event
data to reach the auditing database during the previous polling cycle.
l A value of less than 20 minutes indicates a healthy system.

l A value between 20 minutes and 2 hours indicates a busy system.
Auditing Thread Last Polling Cycle Duration (sec)
l A value of greater than 2 hours indicates a very busy system.
If this state persists and you consider the delay too long, it is recommended that you either
update your deployment to the entire auditing database to receive data at a higher rate or
decrease the number of auditing events that your system tracks.
The percentage of the polling cycle the auditor CMS spends collecting data from auditees.
The remainder is time spent resting between polls. If this value this reaches 100%, the
auditor is still collecting data from the auditees when the next poll is due to begin. This may
Auditing Thread Utilization cause delays in the events reaching the auditing database. If the Thread Utilization
frequently reaches 100%, and remains at this rate for several days, it is recommend you
either update your deployment to allow the auditing database to receive data at a higher
rate, or decrease the number of auditing events that your system tracks.
The average length of time in milliseconds that it took the CMS to perform commit
Average Commit Response Time Since Startup
operations since the server was started. A response time greater than 1000 milliseconds
(msec)
may indicate a need to tune the CMS or the CMS system database.
The average length of time in milliseconds that it took the CMS to perform query operations
Average Query Response Time Since Startup
since the server was started. A response time greater than 1000 milliseconds may indicate
(msec)
a need to tune the CMS or the CMS system database.
Indicates if the Central Manager Server (CMS) as acting as an auditor. A value of “1”
CMS Auditor indicates that the CMS is acting as an auditor. A value of “0” indicates that the CMS is not
acting as an auditor.
Completed Jobs The total number of completed jobs on the CMS since the server started.
Concurrent User Licenses The number of Concurrent User licenses as indicated by the key code.
Indicates whether the CMS has a healthy connection to the auditing database. A value of “1”
indicates that there is a connection. A value of “0” indicates that there is no connection to
Connection to Auditing Database is Established
the auditing database. If the CMS is an auditor, this value should be “1”. If it is “0”,
investigate why a connection to the Auditing database cannot be established.
The number of connections to the CMS system database that the CMS is currently using.
The number of connections that are being currently used may be smaller than or equal to the
number of established system database connections. If the number of established
Currently Used System Database Connections connections and the number of used connections are identical for some time, this may
indicate a bottleneck. Increasing the value for the System Database Connections
Requested property on the "Properties" screen may improve the performance of the CMS.
Tuning the CMS system database may also improve performance.
The number of connections to the CMS system database that the CMS was able to
establish. If a database connection is lost, the CMS attempts to restore the connection. If the
number of established database connections is consistently lower than the number of
system database connections specified by the System Database Connections Requested
Established System Database Connections
property ("Central Management Service" area of the "Properties" screen), it may indicate
the CMS can't acquire additional connections and that the system is not functioning
optimally. A potential solution is to configure the database server to allow more database
connections for the CMS.
Existing Concurrent User Accounts The total number of existing users with concurrent licensing in the cluster.
Existing Named User Accounts The total number of existing users with named licensing in the cluster.
Failed Jobs The number of failed jobs on the CMS since the server started.
The longest length of time in milliseconds that the it took the CMS to perform commit
Longest Commit Response Time Since Startup
operations since the server was started. A response time greater than 10000 milliseconds
(msec)
The longest length of time in milliseconds that the it took the CMS to perform query
Longest Query Response Time Since Startup
operations since the server was started. A response time greater than10000 milliseconds
(msec)
Named User Licenses The number of Named User licenses as indicated by the key code
Number of Commits Since Startup The number of commits to the CMS system database since the server was started.
Number of Objects in CMS System Cache The total number of objects that are currently in the CMS system cache.
Number of Objects in CMS System DB The total number of objects that are currently in the CMS system database.
The total number of database queries since the server was started. A large number may
Number of Queries Since Startup
indicate a more active or heavily loaded system.
The number of concurrent user sessions that are being handled by the CMS when the
Number of Sessions Established by All Users "Metrics" screen loads. The larger this number is, the larger the number of users that are
using the system is. If this number is greater than 250, create an additional CMS.
Number of Sessions Established by Concurrent
The total number of sessions for users with concurrent licensing.
Users
The total number of sessions for users with named
Number of Sessions Established by Named Users
licensing.
The number of concurrent sessions that SAP BusinessObjects Business Intelligence
Number of Sessions Established by Servers platform servers have created with the CMS. If this number is greater than 250, create an
additional CMS.
The number of user logons since the server was started. A large number may indicate a
Number of User Logons Since Startup
more active or heavily loaded system.
The peak number of concurrent user sessions that the CMS has handled since it was
Peak Number of User Sessions Since Startup
started.
The number of jobs that are scheduled, but not ready, to run because the scheduled time or
Pending Jobs
event has not arrived.
The number of requests for the CMS system database that are waiting for an available
connection. If this number is high, consider increasing the value for the System Database
Pending System Database Request
Connections Requested property. Tuning the CMS system database may also improve
performance.
Running Jobs The number of currently running jobs.
Waiting Jobs The number of jobs on the CMS that are scheduled and waiting for free resources.
METRICS SPECIFIC TO THE CRYSTAL REPORTS 2011 REPORT APPLICATION SERVER:

Current Agent Thread Count The number of threads that are currently being processed by the server.
Current Doc Count The number of documents that are currently being processed by the server.
Total Agent Thread Count The number of threads that have been processed by the server since it started.
Total Doc Count The number of documents that have been processed by the server since it started.
METRICS SPECIFIC TO THE EVENT SERVER:

Monitored Files The total number of files that are being monitored by the Event Server.
METRICS SPECIFIC TO THE FILE REPOSITORY SERVERS (INPUT & OUTPUT):

Active Connections The total number of active connections from clients and to other servers.
Active Files The number of files in the File Repository Server that are currently being accessed.
The amount of available disk space, in percentage, on the disk containing the server's executable
Available Disk Space in Root Directory (%)
file.
Available Disk Space in Root Directory The total amount of available space on the disk containing the server's executable file, in
(GB) gigabytes.
Data Sent (MB) The total number of megabytes read from files on the server.
Data Written (MB) The total number of megabytes written to files on the server.
Free Disk Space in Root Directory (GB) The total amount of free space on the disk containing the server's executable file, in gigabytes.
Total Disk Space in Root Directory (GB) The total disk space on the disk containing the server's executable file, in gigabytes.
METRICS SPECIFIC TO THE WEB APPLICATION CONTAINER SERVER:

Number of Full GCs last 15 The number of full Garbage Collections in the last 15 minutes. A rapid increase in this value may indicate a
minutes system under low memory conditions.
Number of Full GCs last 5 The number of full Garbage Collections in the last 5 minutes. A rapid increase in this value may indicate a system
minutes under low memory conditions.
METRICS SPECIFIC TO THE WEB INTELLIGENCE PROCESSING SERVER:

CPU Usage (%) The percentage of total CPU time spent by the server since the server was started.
The number of times that the cache has reached the maximum size allowed on the server since it was
Cache high mark count
started.
Cache Size (KB) The current amount, in kilobytes, of data that is stored in the cache.
Current number of active sessions The current number of sessions that are able to accept requests from clients.
Current number of client calls The current number of CORBA calls that the server is processing.
Current number of sessions The current number of sessions that have been created on the server.
Current number of tasks The current number of tasks that are being executed on the server.
The amount of time, in seconds, that have elapsed since the last request that the server has received from
Idle time (seconds)
a client.
Memory high threshold count The number of times that the high memory threshold has been reached on the server since it was started.
The number of times that the maximum memory threshold has been reached on the server since it was
Memory max threshold count
started.
Number of document swap The number of documents for which a cleanup thread has scheduled swap requests.
Number of documents The number of documents that are currently open on the serve
Number of documents opened from
The number of documents for which the last request result has been directly read from the cache.
cache
Number of swapped documents The number of documents that have been swapped by swap requests.
Number of out of date documents in The number of documents deleted from the cache because there were too old, since the server was
cache started.
The number of times the server has failed to connect to a remote extension service hosted by an Adaptive
Number of remote extension errors
Processing Server.
Number of sessions timeout The number of sessions that have timed out since the server was started.
Number of users The total number of users that are connected to the server.
Total CPU time (seconds) The total CPU time, in seconds, spent by the server since it was started.
Total number of client calls The total number of CORBA calls that the server has received since it was started.
Total number of sessions The number of sessions that have been created on the server since the server was started.
Total number of tasks The total number of tasks that have been executed on the server since it was started.
The total number of threads that have been created since the server was started (asynchronism
Total number of threads
threadpool).
Virtual memory size (MB) The total amount of memory, in megabytes, that are assigned to the server.
Take advantage of SAP Enterprise Support offerings on this topic and more, with an opportunity to collaborate with SAP Support experts at the
Enterprise Support Value Map for Analytics JAM.
Join here: https://support.sap.com/support-programs-services/programs/enterprise-support/academy/valuemaps.html
Keywords
MONITORING, BI4, METRICS, SERVER, MONITOR, HEALTH STATE
Header Data
Released On 14.08.2015 19:35:50
Release Status Released to Customer
Component BI-BIP-ADM User & server configuration, InfoView refresh, user rights
Other Components BI-BIP-MON BI platform monitoring
Priority Normal
Category How To
Product
Product Product Version
SAP BusinessObjects Business Intelligence platform SAP BusinessObjects Business Intelligence platform 4.0

Symptom: Language

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Symptom: Language

Uploaded by

Copyright:

Available Formats

SAP Knowledge Base Article

Caution: Server is slightly overloaded, nearing peak values

METRICS AVAILABLE TO ALL SERVERS

l "0" - Indicates that the health of the metric is bad.

Server Enabled State Indicates whether a service is currently in an “Enabled” status

METRICS COMMON TO MULTIPLE SERVERS:

METRIC SERVERS DESCRIPTION

Adaptive Processing Server

Central Management Server

Crystal Reports 2011 Processing Server

Crystal Reports 2011 Report Application

Dashboard Processing Server

File Repository Server (I&O)

Web Application Container Server

Web Intelligence Processing Server

Central Management Server

Crystal Reports 2011 Processing Server

Crystal Reports 2011 Report Application

Dashoardb Cache Server

Dashboard Processing Server

File Repository Server (I&O)

Web Intelligence Processing Server

Adaptive Processing Server

Central Management Server

Web Application Container Server

Web Intelligence Processing Server

Central Management Server

Crystal Reports 2011 Processing Server

Dashboard Cache Server

Dashboard Processing Server

File Repository Server (I&O)

Web Intelligence Processing Server

Crystal Reports Processing Server

Dashboard Processing Server

Crystal Reports Processing Server

Dashboard Processing Server

Central Management Server

Crystal Reports 2011 Processing Server

Crystal Reports 2011 Report Application

Dashboard Cache Server

Dashboard Processing Server

File Repository Server (I&O)

Web Intelligence Processing Server

Central Management Server

Crystal Reports 2011 Report Application

Dashboard Processing Server

File Repository Server (I&O)

Web Intelligence Processing Server

METRICS SPECIFIC TO THE ADAPTIVE JOB SERVER:

METRIC NAME DESCRIPTION

METRICS SPECIFIC TO THE ADAPTIVE PROCESSING SERVER:

METRIC NAME DESCRIPTION

METRICS SPECIFIC TO THE CENTRAL MANAGEMENT SERVER (CMS):

METRIC NAME DESCRIPTION

l A value of less than 20 minutes indicates a healthy system.

METRICS SPECIFIC TO THE CRYSTAL REPORTS 2011 REPORT APPLICATION SERVER:

METRIC NAME DESCRIPTION

METRICS SPECIFIC TO THE EVENT SERVER:

METRIC NAME DESCRIPTION

METRICS SPECIFIC TO THE FILE REPOSITORY SERVERS (INPUT & OUTPUT):

METRIC NAME DESCRIPTION

METRICS SPECIFIC TO THE WEB APPLICATION CONTAINER SERVER:

METRIC NAME DESCRIPTION