Prior to Intershop version 7.7 the information provided in this document were part of the Administration and Configuration Guide that can be found in the Knowledge Base.
The System Management monitoring module is the main system monitoring tool. Using this module, system administrators can monitor the properties, process information, current threads and requests of all server components in the Intershop Commerce Management system. This information can be used for advanced debugging, profiling and troubleshooting purposes in an Intershop Commerce Management installation.
For details about accessing and using the monitoring module, refer to the System Management online help.
For additional monitoring options, refer to Guide - JMX and MBean Support.
The following tables outline the available monitoring options, sub-section by sub-section.
Prometheus metrics are introduced step by step starting with ICM 7.10
|histogram||Request handler execution times|
Number of connection in database connection pool for given states:
JVM metrics contain information about. The following table contains provided standard metrics of Prometheus library.
Displays general information about the application server (process ID, startup date, cluster ID, server groups), and about its Web front service (port, handler thread number, etc.)
Displays information about the current server process (CPU usage, total process size, in-memory size, used system threads).
Displays the properties that are currently known by the application. This list contains aggregated properties from a number of *.properties files, for example the global and local appserver.properties, orm.properties, all cartridge *.properties files, and staging.properties.
Sensitive properties may be hidden (see).
Sessions and Requests
Displays information about the session management options and session and request statistics for the server.
Enables the retrieval of configuration data from an application server. Configuration values can be retrieved from the scope, domain, application and key (displaying all of the values for each instance of a particular key).
Displays information about the Java Virtual Machine (total heap size, used heap size, used/total heap ratio)
Displays all threads that currently exist in the Java Virtual Machine
Displays all the system properties of the application server's JVM
Displays general information about the ORM cache such as number of cached instances, cache synchronization information, or persistent objects in the cache
Persistent Object Information
Displays information about the selected persistent object on the monitored server (number of instances in cache, default reference type)
Displays information about the registered JDBC drivers
Displays general data source information and Oracle connection cache information
Lists all cartridges loaded on the server and shows basic cartridge information (name, display name, version, build, cartridge directory, JAR files)
Lists all pipelets loaded on the server
Generates a list of duplicate pipelets on the server
Configures and activates/deactivates the Performance Monitor types (request, pipeline, class, managed service, object path, pagelet, pipelet, query, SQL and template) and displays the current monitoring state (active/inactive)
You can also set values to be written to a log.
Compare Performance Monitoring Results
Select a sensor and base report data to make a performance comparison to another report (across all sites).
A sensor is a Request, Pipeline, Class, Managed Service, Object Path, Pagelet, Pipelet, Query, SQL or Template.
Performance by Domain and Site
Select a specific site and display request performance.
Values are returned for hits, total time, effective time, average time minimum time and maximum time.
Performance by Type
Select a specific type of performance measurement and display the values across all sites.
Displays the current background monitoring state and allows for switching it on or off and adjusting the timeout between two measurement cycles
Shows the memory usage of the running server (process memory, JVM memory, ORM cache memory) in graphs
Displays graphical information about the sessions of the running server (total sessions, active sessions, active requests)
Displays detailed information about the performance of the running server (average response time, CPU usage, load factor, thread count)
The Configuration dialog allows for specifying a new monitor pipeline. Intershop strongly recommends to keep the default settings. Unless you have implemented a custom monitor pipeline or added a custom start node to the existing one.
Before you can monitor the database status, you have to execute the script DBMonitorGrants.sql, located in <IS.INSTANCE.LOCAL>/bin.
Displays detailed information about database configuration and performance. Select one of the reports from the list box to display the corresponding information.
Displays information about named resources
Named resources are virtual entities. Every named resource is identified by a unique name. Named resources can have a hierarchical structure.
Displays information about instance resources
Instance resources are created dynamically. Every instance resource represents an instance of a PersistentObject.
Displays information about Intershop Commerce Management processes, such as data replication processes, import processes and scheduled jobs
Displays information about resource acquisition problems
Resource acquisitions problems occur if a process tries to acquire a resource that is already locked by another process.
This section summarizes the service providers that are integrated into your system. The overview page lists the services and their statuses in the site and application server contexts, grouped by service type.
Clicking a service name opens a detail view, which is divided into two tabs. The Monitoring tab shows more, fine-grained operation details, whereas the Maintenance tab provides options to enable/disable, ping or test the current service.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.