LATEST VERSION: 8.2.7 - CHANGELOG
Pivotal GemFire® v8.2

Pulse Quick Start (Embedded Mode)

Pulse Quick Start (Embedded Mode)

Use Pulse in embedded mode to monitor a GemFire deployment directly from a GemFire JMX Manager. By default, the embedded Pulse application connects to the local JMX Manager that hosts the Pulse application. Optionally, configure Pulse to connect to a GemFire system of your choice.

To run Pulse in embedded mode:
  1. Configure a GemFire member to run as a JMX Manager node, specifying the HTTP port on which you will access the Pulse Web application (port 7070 by default). For example, the following command starts a GemFire locator as a JMX Manager node, using the default HTTP port 7070 for the Pulse application:
    gfsh
    gfsh> start locator --name=loc1
    Note: GemFire locators become JMX Manager nodes by default. To start a non-locator member as a JMX Manager node, include the --J=-Dgemfire.jmx-manager=true option. To specify a non-default port number for the HTTP service that hosts the Pulse application, include the --J=-Dgemfire.http-service-port=port_number option when starting the JMX Manager node.

    When the JMX Manager node boots, it starts an embedded Jetty instance and deploys the Pulse Web application at the specified or default HTTP port or 7070 by default.

    gfsh automatically connects to the manager when you start it in this way. If you already started a manager process earlier, use the connect command in gfsh to connect to that process.

  2. Access the embedded Pulse application from a Web browser. If you are connected to the GemFire cluster using gfsh, use the start pulse command to load the correct URL in your browser:
    gfsh> start pulse

    Or, enter the URL http://address:http-service-port/pulse directly in your Web browser, substituting the address and HTTP port of the manager. For example, you access Pulse on the local locator machine from Step 1 at the URL http://localhost:7070/pulse.

  3. If you have configured authentication for the Pulse application, enter the username and password of a valid Pulse account in the login screen. Otherwise, enter the default "admin" in both fields. Click Sign In to continue.

    See Configuring Pulse Authentication.

  4. After you log in, Pulse displays the main cluster view for the local distributed system. See Using Pulse Views.
Note: When running in embedded mode, the Pulse application connects only to the JMX Manager running in the locator or member that hosts Pulse. This enables you to monitor all members of that distributed system.

Hosting Pulse on a Web Application Server

Host Pulse on a dedicated Web application server to make the Pulse application available at a consistent address, or to use SSL for accessing the Pulse application. When you host Pulse in this way, you also configure Pulse to connect to a specific locator or JMX Manager node for monitoring.

To host Pulse on a Web application server:
  1. Set the http-service-port property to zero (-Dgemfire.http-service-port=0) when you start your GemFire JMX Manager nodes. Setting this property to zero disables the embedded Web server for hosting the Pulse application.
  2. Create a pulse.properties file somewhere in the classpath of your Web application server. For example, if you are hosting Pulse on Tomcat, create the pulse.properties file in the $TOMCAT_SERVER/lib directory.

  3. Define the following configuration properties in the pulse.properties file:
    Property Description
    pulse.useLocator Specify "true" to configure Pulse to connect to a GemFire Locator member, or "false" to connect directly to a JMX Manager.

    When Pulse connects to a GemFire locator, the locator provides the address and port of an available JMX Manager to use for monitoring the distributed system. In most production deployments, you should connect Pulse to a locator instance; this allows Pulse to provide monitoring services using any available JMX Manager.

    If you specify "false," Pulse connects directly to a specific JMX Manager. If this manager is not available, the Pulse connection fails, even if another JMX Manager is available in the distributed system.

    pulse.host Specify the DNS name or IP address of the GemFire locator or JMX Manager machine to which Pulse should connect. You specify either a locator or JMX Manager address depending on how you configured the pulse.useLocator property.
    pulse.port Specify the port number of the GemFire locator or the HTTP port number of the JMX Manager to which Pulse should connect. You specify either a locator or JMX Manager port depending on how you configured the pulse.useLocator property.

    If you configured pulse.useLocator=false, then pulse.port must correspond to the http-service-port setting of the JMX Manager.

    pulse.jmxUserName If you configured authentication for the GemFire JMX Manager node, specify a valid JMX user name that the Pulse application will use to authenticate to the JMX Manager.
    Note: The JMX account that Pulse uses must have both read and write privileges.

    See Configuring a JMX Manager for information about configuring authentication for JMX Manager nodes.

    pulse.jmxUserPassword Specify the password of the JMX user account to use for authentication at startup.
    For example, with this configuration Pulse connects to the locator at mylocator[10334] and accesses any available JMX Manager:
    pulse.useLocator=true
    pulse.host=locsrv.gemstone.com
    pulse.port=10334
    pulse.jmxUserName=pulseapp
    pulse.jmxUserPassword=pulsepass
    With this configuration Pulse accesses only the JMX Manager instance at manager1[8080]:
    pulse.useLocator=false
    pulse.host=jmxsrv.gemstone.com
    pulse.port=8080
    pulse.jmxUserName=pulseapp
    pulse.jmxUserPassword=pulsepass
  4. (Optional.) Configure authentication for the Pulse Web application using the instructions in Configuring Pulse Authentication.
  5. Deploy the Pulse Web application to your application server. GemFire installs the pulse.war file in the tools/Pulse subdirectory of your GemFire installation directory. Depending on your application server, you may need to copy the pulse.war file to a deployment directory or use a configuration tool to deploy the file.
  6. Access the Pulse application using the address, port, and application URL that you configure in your Web application server. For example, with Tomcat the default URL is http://address:8080/pulse. Your application server provides options for configuring the address, port, and application name; substitute the correct items to access the deployed Pulse application.

    Pulse connects to the locator or JMX Manager that you configured in the pulse.properties file, authenticating using the credentials that you configured in the file.

  7. If you have configured authentication for the Pulse application, enter the username and password of a valid Pulse account in the login screen. Otherwise, enter the default "admin" in both fields. Click Sign In to continue.

    See Configuring Pulse Authentication.

  8. After you log in, Pulse displays the main cluster view for the distributed system to which it has connected. See Using Pulse Views.

Configuring Pulse Authentication

Pulse requires all users to authenticate themselves before they can use the Pulse Web application. If you have configured JMX authentication on the GemFire JMX Manager node, the Pulse Web application itself may also need to authenticate itself to the GemFire JMX Manager node on startup.

Authenticating the Pulse Application to the JMX Manager

If you run Pulse in embedded mode, the Pulse application runs on the JMX Manager node and no JMX authentication is required. You do not need to specify valid JMX credentials to start an embedded Pulse application.

If you host Pulse on a Web Application server (non-embedded mode) and you configure JMX authentication on the GemFire manager node, then the Pulse Web application must authenticate itself with the manager node when it starts. Specify the credentials of a valid JMX user account in the pulse.properties file, as described in Hosting Pulse on a Web Application Server.

Note: The credentials that you specify must have both read and write privileges in the JMX Manager node. See Configuring a JMX Manager.

Authenticating Pulse Users

Pulse implements user authentication using the Spring security framework. The authentication configuration is specified in the spring-security.xml file, which is stored in the WEB-INF directory of Pulse WAR file. The spring-security.xml file contains bean definitions for role-based resource access, authentication profiles, and authentication handlers. The file also contains a default authentication manager bean definition.

Pulse uses a profile-based authentication configuration. You can can choose to use either the default configuration profile or a custom configuration. The default profile uses the Spring security simple in-memory User Details Service to define a single user with the credentials:
User Name: admin
Password: admin
Role: ROLE_USER
Pulse uses this default authentication profile if you do not specify a profile when starting the application, or if you specify the default profile at startup using the system property:
-Dspring.profiles.active=pulse.authentication.default
You can also configure Pulse to use a custom authentication configuration by specifying activating the custom profile at startup with the system property:
-Dspring.profiles.active=pulse.authentication.custom

Using a custom configuration enables you to use either the simple in-memory User Details Service or an external properties file to authenticate users to the application. Even if you choose to use the default Spring security simple in-memory User Details Service, using a custom authentication configuration enables you to define your own user credentials rather than using the default "admin" account.

Note: GemFire also supports using an LDAP provider for Pulse authentication. See Using LDAP Authentication in Pulse
To configure and use a custom authentication configuration:
  1. Create a directory in which you will store the custom authentication configuration. For example:
    $ mkdir /opt/pulse-config
  2. Ensure that the new directory you created is available on the Java CLASSPATH:
    $ export CLASSPATH=$CLASSPATH:/opt/pulse-config
  3. Create a new text file named pulse-authentication-custom.xml in the new directory:
    $ touch /opt/pulse-config/pulse-authentication-custom.xml
  4. Use a text editor to add the bean definitions for the authentication managers and providers that you want to use. The following listings show the example file contents for using the in-memory User Details Service and an external properties file:
    Example pulse-authentication-custom.xml for Spring simple in-memory User Details Service
    <beans:beans >
      <authentication-manager>
        <authentication-provider>
          <user-service id="userDetailsService">
            <user name="john" password="johnspassword" authorities="ROLE_USER " />
            <user name="bob" password="bobspassword" authorities="ROLE_USER" />
          </user-service>
        </authentication-provider>
      </authentication-manager>
    </beans:beans>
    Example pulse-authentication-custom.xml for external properties file
    <beans:beans >
      <authentication-manager>
        <authentication-provider>
          <user-service properties="classpath:pulse-users.properties">
          </user-service>
        </authentication-provider>
      </authentication-manager>
    </beans:beans>
    With file-based authentication mechanism, you define the names and passwords for valid Pulse users in a pulse-users.properties file, which must be available in the classpath of the Pulse application. Each line in the pulse-users.properties file defines the username, password, and access level for a Pulse user with the format:
    username=password,role,{enabled | disabled}
    The role entry must correspond to a valid Spring security role. For example, this entry shows the default "admin" user enabled with basic user access:
    admin=admin,ROLE_USER,enabled
  5. When you start GemFire members, specify the custom authentication profile using the -Dspring.profiles.active=pulse.authentication.custom system property. For example:
    gfsh> start server --name=server1 --J=-Dspring.profiles.active=pulse.authentication.custom
  6. Start Pulse and log in using credentials that are authorized in the custom configuration.

Using LDAP Authentication in Pulse

This section provides instructions for using LDAP authentication with Pulse in either embedded and non-embedded mode.

Embedded Mode (Jetty)

To configure LDAP for Pulse:

  1. Create a directory in which you will store the LDAP authentication configuration. For example:
    $ mkdir /opt/pulse-config
    The directory name and location are up to you-- just make sure you use the same name when specifying the CLASSPATH for the GemFire JMX Manager process.
  2. Create a file named pulse-authentication-custom.xml with contents similar to the following and place it under the directory you created in step 1. For example:
    <beans:beans xmlns="http://www.springframework.org/schema/security"
       	xmlns:beans="http://www.springframework.org/schema/beans"
       	xmlns:context="http://www.springframework.org/schema/context"
       	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       	xsi:schemaLocation="http://www.springframework.org/schema/beans
       	http://www.springframework.org/schema/beans/spring-beans-3.2.xsd
                   http://www.springframework.org/schema/security
                   http://www.springframework.org/schema/security/spring-security-3.1.xsd
                   http://www.springframework.org/schema/context
       	http://www.springframework.org/schema/context/spring-context-3.2.xsd">
       	
            <ldap-server url="ldap://ldap.gemstone.com:389/dc=gemstone,dc=com" />
    
            <authentication-manager>
               <ldap-authentication-provider user-dn-pattern="uid={0},ou=ldapTesting"  
                group-search-base="cn=PULSEUSER,ou=Groups" group-search-filter="memberUid={1}">
               </ldap-authentication-provider>
           </authentication-manager>
     
    </beans:beans>
    LDAP authentication in Pulse is hardcoded to use the PULSEUSER user group. Make sure you have have created users for this group.
  3. When starting the JMX Manager from gfsh, use the following commands:
    gfsh>start locator --name=loc --J=-Dspring.profiles.active=pulse.authentication.custom --classpath=/opt/pulse-config
    or
    gfsh>start server --name=server1 --J=-Dspring.profiles.active=pulse.authentication.custom --classpath=/opt/pulse-config
  4. Start Pulse and log in using credentials that are authorized in the LDAP configuration.

Non-Embedded (Standalone Web Server) Mode (Tomcat)

To configure LDAP for Pulse:

  1. Create a directory in which you will store the LDAP authentication configuration. For example:
    $ mkdir /opt/pulse-config
  2. The directory name and location of the Pulse configuration files are up to you-- just make sure you use the same name when specifying the CLASSPATH for the Tomcat server.
  3. Pass in the Spring profile when starting the web server. In Tomcat, all the VM arguments are set in the variable CATALINA_OPTS, which you can define in your environment configuration file setenv.bat or setenv.sh.

    For example, under %CATALINA_HOME%/bin or $CATALINA_HOME/bin, you can create a setenv batch file or script file (if not already present) that sets the following. On Windows:

    set CATALINA_OPTS=-Dspring.profiles.active=pulse.authentication.custom
    set "CLASSPATH=C:\pulse-config"
    or in Unix/Linux:
    CATALINA_OPTS=-Dspring.profiles.active=pulse.authentication.custom
    export CATALINA_OPTS
    CLASSPATH=$CLASSPATH:/opt/pulse-config
  4. Create a file named pulse-authentication-custom.xml with contents similar to the following and place it under the directory you created in step 1. For example:
    <beans:beans xmlns="http://www.springframework.org/schema/security"
       	xmlns:beans="http://www.springframework.org/schema/beans"
       	xmlns:context="http://www.springframework.org/schema/context"
       	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       	xsi:schemaLocation="http://www.springframework.org/schema/beans
       	http://www.springframework.org/schema/beans/spring-beans-3.2.xsd
                   http://www.springframework.org/schema/security
                   http://www.springframework.org/schema/security/spring-security-3.1.xsd
                   http://www.springframework.org/schema/context
       	http://www.springframework.org/schema/context/spring-context-3.2.xsd">
       	
            <ldap-server url="ldap://ldap.gemstone.com:389/dc=gemstone,dc=com" />
    
            <authentication-manager>
               <ldap-authentication-provider user-dn-pattern="uid={0},ou=ldapTesting"  
                group-search-base="cn=PULSEUSER,ou=Groups" group-search-filter="memberUid={1}">
               </ldap-authentication-provider>
           </authentication-manager>
     
    </beans:beans>
    LDAP authentication in Pulse is hardcoded to use the PULSEUSER user group. Make sure you have have created users for this group.
  5. Deploy the application and start the server.

Configuring Pulse to Use HTTPS

You can configure Pulse to use HTTPS in either embedded or non-embedded mode.

In non-embedded mode where you are running Pulse on a standalone Web application server, you must use the Web server's SSL configuration to make the HTTP requests secure.

In embedded mode, the GemFire uses an embedded Jetty server to host the Pulse Web application. To make the embedded server use HTTPS, you must configure the following GemFire configuration parameters in gemfire.properties or gfsecurity-properties:

  • http-service-ssl-enabled
  • http-service-ssl-require-authentication
  • http-service-ssl-protocols
  • http-service-ssl-ciphers
  • http-service-ssl-keystore
  • http-service-ssl-keystore-password
  • http-service-ssl-keystore-type
  • http-service-ssl-truststore
  • http-service-ssl-truststore-password

See SSL for details on configuring these parameters.

The above parameters apply to all HTTP services hosted on the JMX Manager, which includes the following:

  • Developer REST API service
  • Management REST API service (for remote cluster management)
  • Pulse monitoring tool

When the above properties are configured, all HTTP services become SSL-enabled and you must configure your client applications accordingly. For SSL-enabled Pulse, you will need to configure your browsers with proper certificates.

Using Pulse Views

Pulse provides a variety of different views to help you monitor GemFire clusters, members, and regions.

The following sections provide an overview of the main Pulse views:

Cluster View

The cluster view is a high-level overview of the GemFire distributed system. It is displayed immediately after you log into Pulse. Information displays around the perimeter of the cluster view show statistics such as memory usage, JVM pauses, and throughput. You can use the cluster view to drill down into details for individual members and regions in the distributed system.


Use these basic controls while in Cluster view:
  1. Click Members or Data to display information about GemFire members or data regions in the distributed system.
  2. Click the display icons to display the GemFire members using icon view, block view, or table view. Note that icon view is available only when displaying Members.

    For example, the following shows GemFire Members displayed in table view:

    • While in block view or table view, click the name of a GemFire member to display additional information in the Member View.
    • Click Topology, Server Groups, or Redundancy Zones to filter the view based on all members in the topology, configured server groups, or configured redundancy zones.

    The following shows GemFire Regions displayed in table view:

    • While in block view or table view, click the name of a GemFire region to display additional information in the Region View.
  3. While in icon view, click a host machine icon to display the GemFire members on that machine.
  4. In the Alerts pane, click the severity tabs to filter the message display by the level of severity.

Cluster View Screen Components

The following table describes the data pieces displayed on the Cluster View screen.
Screen Component Description
Cluster Status Overall status of the distributed system being monitored. Possible statuses include Normal, Warning, or Severe.
Total Heap Total amount of memory (in GB) allocated to the Java heap across all members.
Members Total number of members in the cluster.
Servers Total number of servers in the cluster.
Clients Total number of clients in the cluster.
Locators Total number of locators in the cluster.
Regions Total number of regions in the cluster.
Functions Total number of functions registered in the cluster.
Subscriptions Total number of client event subscriptions.
Cluster Members Graphical, block, or table view of the members in the cluster.
Topology Organizes cluster members by DistributedMember Id.
Server Groups Organizes cluster members by server group membership. If no server groups are configured, all members appear under the "Default" server group.
Redundancy Zones Organizes cluster members by redundancy zones. If no redundancy zones are configured, all members appear under the "Default" zone.
Host Machine When you mouse over a machine icon in Topology View, a pop-up appears with the following machine statistics:
  • CPU Usage. Percentage of CPU being used by GemFire processes on the machine.
  • Memory Usage. Amount of memory (in MB) being used by GemFire processes.
  • Load Avg. Average number of threads on the host machine that are in the run queue or are waiting for disk I/O over the last minutes. Corresponds to the Linux System statistic loadAverage1. If the load average is not available, a negative value is shown.
  • Sockets. Number of sockets currently open on the machine.
Member When you mouse over a member icon in Graphical View, a pop-up appears with the following member statistics:
  • CPU Usage. Percentage of CPU being used by the GemFire member process.
  • Threads. Number of threads running on the member.
  • JVM Pauses. Number of times the JVM used by the member process has paused due to garbage collection or excessive CPU usage.
  • Regions. Number of regions hosted on the member process.
  • Clients. Number of client currently connected to the member process.
  • Gateway Sender. Number of gateway senders configured on the member.
  • Port. Server port of the cache server member where clients can connect and perform cache operations.
  • GemFire Version. The version of the GemFire member.
Member In List View, the following data fields are displayed for each member:
  • ID. DistributedMember Id of the member.
  • Name. Name of the member.
  • Host. Hostname or IP address where the member is running.
  • Heap Usage. Amount of JVM heap memory being used by the member process.
  • CPU Usage. Percentage of CPU being used by the GemFire member process.
  • Uptime. How long the member has been up and running.
  • Clients. Number of clients currently connected to the member. It will have a value only if the member acts as a CacheServer.
Key Statistics Displays a few key performance measurements of the distributed system (over the last 15 minutes).
Write/Sec Number of write operations per second that have occurred across the cluster. Each put/putAll operation counts as a write; for example, a putAll of 50 entries is counted as one write.
Read/Sec Number of read operations per second that have occurred across the cluster.
Queries/Sec Number of queries per second that have been executed across the cluster.
No. of JVM Pauses Number of times the JVM has paused during the last five minutes to perform garbage collection.
Disk Throughput Total disk throughput for all disks in cluster.
Alerts View Displays alerts for the cluster.

Member View

When you select an individual GemFire member in Cluster View, Pulse displays the regions available on that member, as well as member-specific information such as the configured listen ports.


Use these basic controls while in Member View:
  1. Click the display icons to display regions using block view or table view.
  2. Use the drop down menu to select a specific member or search for specific members by name.
  3. Click Cluster View to return to Cluster View. See Cluster View.
  4. Click Data Browser to query region data. See Data Browser.

Member View Screen Components

The following table describes the data elements displayed on the Member View screen.
Screen Component Description
Member Status Overall status of the member being monitored. Possible statuses include Normal, Warning, or Severe.
Regions Total number of regions hosted on the member.
Threads Total number of threads being executed on the member.
Sockets Total number of sockets currently open on the member.
Load Avg. Average number of threads on the member that are in the run queue or are waiting for disk I/O over the last minute. Corresponds to the Linux System statistic loadAverage1. If the load average is not available, a negative value is shown.
Clients Current number of client connections to the member.
Member Regions Block or table view of the regions hosted on the member.
Regions When you mouse over a region in block view, a pop-up appears with the following data fields:
  • Name. Region name.
  • Type. For example, REPLICATE, PARTITION.
  • EntryCount. Number of entries in the region.
  • EntrySize. The aggregate entry size (in bytes) of all entries. For replicated regions this field will only provide a value if the eviction algorithm has been set to EvictionAlgorithm#LRU_ MEMORY. All partition regions will have this value. However, the value includes redundant entries and will also count the size of all the secondary entries on the node.
Regions In table view, the following fields are listed for each region:
  • Name. Region name.
  • Type. For example, REPLICATE, PARTITION.
  • EntryCount. Number of entries in the region.
  • EntrySize. The aggregate entry size (in bytes) of all entries. For replicated regions this field will only provide a value if the eviction algorithm has been set to EvictionAlgorithm#LRU_ MEMORY. All partition regions will have this value. However, the value includes redundant entries and will also count the size of all the secondary entries on the node.
  • Scope. Scope configured for the region.
  • Disk Store Name. Name of disk stores (if any) associated with the region.
  • Disk Synchronous. True if writes to disk are set to synchronous and false if not. This field reflects the configured disk-synchronous region attribute.
  • Gateway Enabled. Whether gateway sender and receiver configurations have been defined on members hosting this region.
Member Clients In table view, the following fields are listed for each client:
  • Id. DistributedMember ID of the client process.
  • Name. Name of the client process.
  • Host. Hostname or IP address of the client process.
  • Connected. Whether the client process is currently connected to the member.
  • Queue Size. The size of the queue used by server to send events in case of a subscription enabled client or a client that has continuous queries running on the server.
  • CPU Usage. Percentage of CPU being used by the client process.
  • Uptime. Amount of time the client process has been running.
  • Threads. Threads being used by the member clients
  • Gets. Total number of successful get requests completed.
  • Puts. Total number of successful put requests completed.
Key Statistics Displays a few key performance measurements for the member (over the last 15 minutes).
% CPU Usage Percentage of CPU used by the member.
Read/Sec Number of read operations per second that have occurred on the member.
Write/Sec Number of write operations per second that have occurred on the member. Each put/putAll operation counts as a write; for example, a putAll of 50 entries is counted as one write.
Memory Usage Total memory used on the member in MB.
No. of JVM Pauses Number of times the JVM has paused during the last five minutes due to garbage collection or excessive CPU usage.
Disk Throughput Rate of disk writes on the member.

Region View

The Pulse Region View provides a comprehensive overview of all regions in the GemFire distributed system:


Use these basic controls while in Region View:
  1. Click the display icons to display all members that host the region using block view or table view.

    (Click the name of a member to change to that member's Member View.)

  2. Search for specific members that host the current region.
  3. Hover over a member name to display information such as the region entry count, entry size, and throughput on that member.
  4. Click Cluster View or Data Browser to go to those screens.

Region View Screen Components

The following table describes the data elements displayed on the Region View screen.
Screen Component Description
Region Members Lists information about GemFire members that host the region, either in block view or table view.
Region Member (Detail View) When you hover over a region member in block view, a pop-up appears with the following data fields:
  • Member Name. The name of the GemFire member hosting the region.
  • EntryCount. Number of entries for the region on that member.
  • EntrySize. The aggregate entry size (in bytes) of all entries on that member. For replicated regions this field will only provide a value if the eviction algorithm has been set to EvictionAlgorithm#LRU_ MEMORY. All partition regions will have this value. However, the value includes redundant entries and will also count the size of all the secondary entries on the node.
  • Accessor. Indicates whether the member is an accessor member.
  • Reads/Writes. Summary of reads and writes served from memory and from disk stores over the last 15 minutes.
Region Member (Table View) In table view, the following fields are listed for each region member:
  • ID. The unique member ID.
  • Name. Region name.
  • Host. Member hostname.
  • Heap Usage. The total amount of heap used on the member in MB.
  • CPU Usage. CPU usage as a percent of available CPU.
  • Uptime. The amount of time elapsed since the member started.
  • Accessor. Indicates whether the member is an accessor member.
Region Detail When you have selected a region, the right hand pane displays the following information about the region:
  • Name. Name of the region.
  • Region Path. Path for the region.
  • Type. For example, REPLICATE, PARTITION
  • Members. Number of members that are hosting the region.
  • Empty Nodes. Nodes where the region DataPolicy is defined as EMPTY or where LocalMaxMemory is set to 0.
  • Entry Count. Total number of entries in the region.
  • Disk Usage. Persistent data usage.
  • Persistence. Indicates whether the region's data is persisted to disk.
  • Memory Usage. The amount of memory used and total available memory (also shown as a percentage).
  • Reads/Writes. Summary of reads and writes served from memory and from disk stores over the last 15 minutes.

Data Browser

The Pulse Data Browser enables you to query region data. Note that there are two key attributes available on DistributedSystemMXBean that you can use to configure limits for the result sets displayed in Data Browser:
  • QueryResultSetLimit limits the number of rows that Data Browser queries return. 1000 rows are displayed by default.
  • QueryCollectionsDepth limits the number of elements of a collection that Data Browser queries return. This attribute applies to query results contain collections such as Map, List, and so forth. The default value is 100 elements.

See the com.gemstone.gemfire.management.DistributedSystemMXBean JavaDocs for information on available MBean methods and attributes.

The following shows an example Data Browser view:


Use these basic controls while in Data Browser view:
  1. Search for the name of a specific region.
  2. Select one or more regions to display the GemFire members that host those regions. The hosting GemFire members appear in the Region Members section.
  3. Select one or more members from the Region Members section to restrict query results to those members.
  4. Type in the text of a query to execute. See Querying.
  5. Display a list of previously-executed queries. Double-click on a query from the history list to copy it to the Query Editor, or delete the query from your history.
  6. Execute your query or clear the contents of the Query Editor.
  7. View the current query results.
  8. Export the query results to a text file.
  9. Return to Cluster View.

Alerts Widget

The Alerts Widget appears in the right portion of the screen and displays a list of alerts.

The alerts displayed for the cluster appear based on the alertLevel field set in the DistributedSystemMXBean. By default, log messages with the level of SEVERE are shown as alerts. You can modify the level by using the DistributedMXBean.changeAlertLevel method. See System Alert Notifications ofr more information.

Use these basic controls in the Alerts Widget:
  1. Select an alert level to view only alerts with a specific severity.
  2. Enter text in the search box to filter the list of alerts.
  3. Select an alert and click Clear to remove it from the alert list.
  4. Click Clear All to remove all alerts from the widget.
  5. Double-click an alert to open a pop-up window that displays the full text of the alert message.
  6. Click the check mark in an alert pop-up window to acknowledge the alert. Acknowledged alerts display a check mark in the list of alerts.
  7. Triple-click the alert in the pop-up or in the alert list to select the message text. You can then copy and paste the text into another application.
  8. Click the X to close the pop-up alert window.