Pulse Comparison table (on-premise vs IBM Cloud)
Pulse can monitor many IBM Planning Analytics (TM1) instances. They can be self-hosted (on-premise or on your private cloud such as AWS, Google Cloud…) or on IBM Cloud (PA Cloud and PAaaS).
It does not matter where Pulse is installed but what is important is where TM1 is hosted.
A couple of Pulse features require direct access to the TM1 server and therefore are not available when your TM1 instances are on the IBM PA Cloud.
Features that differ by environment
Most of Pulse works the same way everywhere. The table below lists only the features whose availability depends on where TM1 is hosted:
Feature | PA Self-hosted | IBM PA Cloud (v11) | IBM PAaaS (v12) |
|---|---|---|---|
24/7 Live Monitoring (ℹ️) | ✔️ | ✔️ | ✔️ *Server logs are currently not available |
Chore & Process History | ✔️ | ✔️ | ❌ *Server logs are currently not available |
Automated change tracking (ℹ️) | ✔️ | ✔️ | ✔️ *Only when the documentation is executed |
Monitoring CPU, RAM (servers) | ✔️ | ✔️ | ❌ |
Monitoring disk space (servers) | ✔️ | ❌ | ❌ |
Offline migration (ℹ️) | ✔️ | ❌ | ❌ |
Stop/Start instances | ✔️ | ❌ | ❌ |
Tracking TM1 Web usage (ℹ️) | ✔️ | ❌ | ❌ |
All other Pulse features (listed below) | ✔️ | ✔️ | ✔️ |
All other Pulse features
These are available in every environment, whether TM1 is self-hosted, on the IBM PA Cloud (v11) or on IBM PAaaS (v12):
Separation of duties (built-in security)
Monitoring CPU, RAM (TM1 instances)