Jul 3, 2021
Pulse for TM1 health check
Most of the errors when using the Pulse migration features are coming from misconfiguration. If you haven’t used Pulse for a while, it is recommended to go through this checklist before using the Pulse migration feature:
1 – Check Pulse version
We recommend to always use the latest version of Pulse. You can find the list of all Pulse releases in the following forum post:
When doing the Pulse migration between two Pulse servers, the Pulse version needs to be the same on both Pulse.
2 – Check Pulse status page
The Status tab of the Pulse About page will help you to check if all connections from Pulse to its database, the Pulse monitors, and the Elastic cluster are working.
Related help articles:
- Connecting to the Pulse database
- Connecting a Pulse Monitor
- Pulse Monitor Settings
- Understanding the Pulse Elasticsearch data
3 – SMTP settings
In order for Pulse to send emails when an alert is triggered, Pulse needs the SMTP server settings. Go to Pulse Configuration page and check the Email panel as below:
4 – Notification groups
Check who is set up in the Notifications group, i.e who is going to receive an email when an alert is triggered:
5 – Recommended alerts
Alerts is one of the key features of Pulse. It enables you to be pro-active, to be able to know when an issue will occur and act accordingly. In the following article, you can find the recommended alerts:
6 – Check if documentation was updated last night
The documentation is the backbone of Pulse. It needs to run every day (by default at 1:45 am). If the documentation is not running, it means that Pulse is not fully working. In the model spotlight, select an instance and you will see when was the last update of the documentation.
All the reasons why the Pulse documentation would not complete are gathered in the following article:
Enabling system alerts
Pulse v6 introduced system alerts to get a notification when one component of Pulse is not working. More information is available in the following article:
When Pulse connects to the IBM Cloud, there is one more System Alert that needs to be configured on the Environment page for each server:
All users in this group will get an email when the credentials expire. Once the credentials expire, someone with an IBM ID (with TM1 Admin access) needs to click the Login button and enter the credentials.