What’s new in Pulse v6

This release is the most important release of Pulse since it’s creation in 2014. Pulse was optimized for the TM1 REST API, enabling one single application server to monitor many TM1 servers.

This version includes new features such as the Pulse Explorer (bringing a new way to easily view what is happening on all your TM1 instances second per second) and support for the IBM Cloud.

When working with multiple TM1 servers, you can choose between installing one Pulse server that will monitor many TM1 servers or installing Pulse on each server. There are many advantages of a centralized Pulse server such as:

• Pulse configuration is managed in one location.
• All information about all TM1 instances is stored in the same database.
• Migration can happen between TM1 servers without having to download from one Pulse server then upload the package to another.
• Upgrading will be quicker as only one Pulse server will need to be upgraded.

Thanks to the power of the TM1 REST API, Pulse 6 can monitor TM1 instances from any platform (on-premise, on the IBM Cloud, or any other cloud vendors). Two options are available for customers running TM1 on the IBM Cloud:

• Running Pulse 6 on the cubewise cloud.
• Running Pulse 6 on their own server.

Pulse 6 includes the open source version of Elasticsearch and Kibana. Two new services will be installed:

• Pulse Elasticsearch: This service populates the built-in Elasticsearch database. The Elasticsearch data can then be consumed by Pulse Kibana.
• Pulse Kibana: This service manages the Pulse Explorer client to explore and visualize Pulse data.

Elasticsearch provides more granularity and allows Pulse to drill into detailed historical information. Pulse Elasticsearch and Kibana can be installed on a separate server.

Thanks to Elasticsearch, Pulse data is now easily accessible second by second:

The new Pulse Explorer feature allows you to easily build your own dashboards. Pulse 6 includes a set of dashboards to get you started with Kibana:

Pulse 6 fully supports hierarchies. Hierarchies are processed by Pulse as separate dimensions. All features that can be applicable to dimensions are available to hierarchies such as documentation, change tracking, and migration.

The Pulse Dashboard shows the key information about the server selected from the dropdown. A new feature called the Dashboard Editor has been added to edit the dashboard. For example, you can choose to show the data from multiple servers:

Pulse 6 makes it easier to migrate TM1 objects between servers. As Pulse can monitor many TM1 instances from different servers, there is no need to download and then upload a migration package anymore. When creating or executing a migration package, you will choose the target server and then the target instance.

A new Servers administration page has been added to manage the information of the TM1 servers that Pulse needs to be monitor.

A new Status page has been added to help monitor the health of Pulse. From this page you can:

• Quickly see if the connection between the TM1 servers and Pulse is working.
• The heath of the Elasticsearch cluster.
• The size of the Pulse and Elasticsearch databases.

A new alert called Enable Pulse Monitor Connectivity Alert can be activated per server. Pulse will send an alert if it can’t connect anymore to the TM1 server.

Two new system alerts have been added:

• Enable Database Connectivity Alert: Send an email notification when there is an issue with the database.
• Enable ElasticSearch Connectivity Alert: Send an email notification when there is an issue with the Elastisearch.

To learn more about Pulse 6 and to understand the steps to upgrade your environments, please go through the Pulse 6 getting started guide below:

• Getting started with Pulse

Do you want to know more about Pulse watch the introduction video:

• How to optimize your TM1 licenses
• How change tracking gives you the confidence to do more development
• Sending email alerts from TM1