The size of the Elastic Cluster can be found in the Pulse About page:

This article explains the steps to migrate Pulse 5 data from one server to a new server where Pulse 6 is installed.

Pulse for TM1 allows you to track how TM1 Web is being used, each time a user moves between web sheets and cube views it is logged to the Pulse database. Quickly see the current open web sheets so you can determine what is causing long running queries or slowing the system.

Once the Pulse Monitor has been installed on a separate server, the next step is to connect it to the main Pulse Application Server.

To connect to a TM1 instance with Pulse 6 or later, Pulse uses the TM1 REST API, you need to make sure first that the TM1 REST API is enabled for each instance and accessible from the Pulse server, more information here:

To get Pulse up and running you need to follow the steps of the Setup Wizard. Before you start the Setup Wizard you should have the following information ready: