Pulse issueshttps://support.cubewise.com/code/pulse/-/issues2024-03-21T02:22:17Zhttps://support.cubewise.com/code/pulse/-/issues/4499ER: add a duration threshold for memory and CPU alerts2024-03-21T02:22:17ZswER: add a duration threshold for memory and CPU alerts**Is your feature request related to a problem? Please describe.**
The CPU alert in its current form is not useful and consequently never used as CPU can spike to 100% (or close to) multiple times per day for all sorts of reasons on a T...**Is your feature request related to a problem? Please describe.**
The CPU alert in its current form is not useful and consequently never used as CPU can spike to 100% (or close to) multiple times per day for all sorts of reasons on a TM1 server that are within normal operating bounds (e.g. loading data with parallel threads, any operation involving MTQ such as query execution or processing feeders). Therefore this alert is never configured as it would lead to multiple false positive reports. What is required to make this alert useful is a _duration threshold seconds_ e.g. set CPU at 99 and duration at 120 seconds would mean the alert will only be triggered if average CPU exceeds 99% for a time window of 120 seconds or longer.
Similarly the Memory alert (while already useful) would be **_much more useful_** if it also had a _duration threshold seconds_ parameter as this would vastly reduce false positive alerts due to memory spiking for short durations. E.g. in some systems memory can spike above 90% for short duration due to processes which are external to TM1 like data loads via tm1py where python uses a lot of memory, or backups where large files are temporarily cached in memory while writing to disk.
**Describe the solution you'd like**
Add configurable duration parameter to BOTH CPU and Memory alert types.
**Additional context**
This would improve monitoring quality by eliminating false positive alerts. The problem with false positives is that they create background noise and increase the risk that legitimate alerts will be ignored or not actioned.6.3.2Elias GonzalezElias Gonzalezhttps://support.cubewise.com/code/pulse/-/issues/4481Regarding Pulse alerts for CPU or memory.2024-03-21T02:21:27Zli FinchRegarding Pulse alerts for CPU or memory.**Is your feature request related to a problem? Please describe.**
We set CPU and memory alerts in Pulse, but sometimes the server's CPU load increases by 90+% in an instant and then drops. At this point, we will receive an email from P...**Is your feature request related to a problem? Please describe.**
We set CPU and memory alerts in Pulse, but sometimes the server's CPU load increases by 90+% in an instant and then drops. At this point, we will receive an email from Pulse, warning that the CPU usage is 90+% and has exceeded the threshold of 90+%. This requires us to frequently check the server, but in reality, the server is functioning normally.
**Describe the solution you'd like**
I hope that Pulse's alert setting has a feature that can monitor CPU or memory usage when it exceeds a threshold and lasts for a period of time(Customizable), and then Pulse sends out the alert email. We don't want Pulse to send emails every time the threshold is triggered, as this can cause us to receive a lot of alerts and overlook the truly problematic emails.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.6.3.2Shanoo ChauhanShanoo Chauhanhttps://support.cubewise.com/code/pulse/-/issues/4101Enhancement PULSE - Create alerts for persistent situations2024-03-21T02:23:30ZMédard ATANNONEnhancement PULSE - Create alerts for persistent situationsHello Team,
It's will be intersting to have the possibility to create alert to flow some persitent situations. For example :
- **"CPU consumption > 90 since 5 min"**
- **"RAM consumption > 80 since 600 seconds"**
Thank you,Hello Team,
It's will be intersting to have the possibility to create alert to flow some persitent situations. For example :
- **"CPU consumption > 90 since 5 min"**
- **"RAM consumption > 80 since 600 seconds"**
Thank you,6.3.2VincentVincenthttps://support.cubewise.com/code/pulse/-/issues/4457Removal of Existing Objects with Migration Package (CleanUp of Legacy/Existing)2024-02-22T05:56:01ZDonovan AustinRemoval of Existing Objects with Migration Package (CleanUp of Legacy/Existing)**Is your feature request related to a problem? Please describe.**
We have situations where we update/enhance modules within TM1.
In this process, we sometimes have to Split current existing Processess into more than one process.
This ...**Is your feature request related to a problem? Please describe.**
We have situations where we update/enhance modules within TM1.
In this process, we sometimes have to Split current existing Processess into more than one process.
This results in the process name changing to align with each of their actions, however as Pulse only 'creates' objects, we sit with a situation where we have old processess/dimensions etc staying in our PRD Instance thats not needed.
If possible, can there be means, via the deployment package to REMOVE certain objects in the target instance with the deployment?
**Describe the solution you'd like**
Have the Migration Package have two primary tasks:
Migration Objects - existing.
Remove Objects - New (Remove from Target Instance to avoid sitting with unused/legacy objects that have been replaced)
**Describe alternatives you've considered**
Deploy cleanup process with the migration package to remove objects via CommandPompt etc as we don't have Admin nor Access to DB.
However, then we sit with the Cleanup processes in PRD. Last option would be to go create a primary cleanup process with multiple parameters and run that individually for all objects to be deleted post deployment.https://support.cubewise.com/code/pulse/-/issues/4416Trace commits back to migration package2024-02-09T05:06:45ZgngTrace commits back to migration package**Is your feature request related to a problem? Please describe.**
(Posted the question on the Cubewise Forum. But didn't get a reply yet so raising this here)
https://forum.cubewise.com/t/audit-trace-commits-back-to-migration-package/6...**Is your feature request related to a problem? Please describe.**
(Posted the question on the Cubewise Forum. But didn't get a reply yet so raising this here)
https://forum.cubewise.com/t/audit-trace-commits-back-to-migration-package/6180
A client using Pulse needs to provide proof to IT audit on the changes made in production.
The idea is to look at an object changed, find out the deployment package used, and see all the related objects modified for the change request.
The manual description on the migration package will also reference the Change Request ID related for this deployment
allowing them to reference all associated documentation from: requirements, test results, sign-off, and post implementation verification.
**Describe the solution you'd like**
Can a migration package also display the commits of each modified object to allow easy navigation to it to view the code difference.
Vice versa, looking at an object commit, can there be a link that navigates to the migration package used to deploy.
Currently the user has to associate the commits and migration package manually.
(/uploads/8f4dd8e3a32e30946497623d43fde8f8/Commit_and_Migration.png)https://support.cubewise.com/code/pulse/-/issues/4403Pulse - Full Package Roll Back (vs Object by Object)2024-02-05T05:52:02ZDonovan AustinPulse - Full Package Roll Back (vs Object by Object)**Is your feature request related to a problem? Please describe.**
Not a problem, but a Feature request.
We Promoted a Package to our PRD Env, however through our test case and UAT Sign off, a specific scenario was missed causing the p...**Is your feature request related to a problem? Please describe.**
Not a problem, but a Feature request.
We Promoted a Package to our PRD Env, however through our test case and UAT Sign off, a specific scenario was missed causing the promoted module to give issues.
We then had to Roll-Back these items as it impacted a core function but discovered that one can't roll back a **Package as a whole**. We had to roll back Object by Object which caused more interim issues (This is time consuming sometimes causing the problem to get worst before it gets better and we weren't able to notify an outage.
**Describe the solution you'd like**
In a Package View, have the option to Roll Back the full Package with all their objects.
My assumption would be that the existing object version/timestamp etc is stored when upgrading and those objects can just be re-migrated back into the system upon rollback.
**Describe alternatives you've considered**
We started a backup of the PRD Instance, created a Package from the backup instance and promoted those objects back to Live PRD (As a rollback).https://support.cubewise.com/code/pulse/-/issues/4400Can't see who approved a package (Can only see the Notification group)2024-02-07T02:05:45ZDonovan AustinCan't see who approved a package (Can only see the Notification group)
**1. Key information:**
- Company / Customer Name: Digital Outsource Services
- OS and Version: Windows 2016
- TM1/PA Version: N/A
- Pulse Version 6.3.1
- Browser Chrome with ad Login
Firstly, we appreciate the Approval Function ...
**1. Key information:**
- Company / Customer Name: Digital Outsource Services
- OS and Version: Windows 2016
- TM1/PA Version: N/A
- Pulse Version 6.3.1
- Browser Chrome with ad Login
Firstly, we appreciate the Approval Function in Pulse, but we require some items to ensure it covers all the required SOX Controls.
1 - When a Package Approval is requested, one indicates a Notification Group who receives an email. (**This is perfect**)
2 - When a person, with Approval Rights (Per security Group) approves a Package that allows the execution of the Package. **Thats perfect** except for enhancement request #4399
_Here's where the problem with the Auditors start._
3 - On the Approval Page, one can't see **WHO** actually approved the request. How can one identify who actually approved the migration.
4 - In the actual Migration Package, it indicates in the 'Approval History' that the item was approved, but again one can't see **WHO** actually approved the package. It only provides a Notification Group who can exist out of more than one person.
5 - The Auditors then asked who's in our Approval Notification group as that should pinpoint who would have possibly approved it, but then they identified that the list in that group can be changed on demand without history/last modified. So in a Year that group might change and one won't have record who approved the item.
**Proposals/Solution**
1 - Approval Requests tab, add a column indicating the **individuals name** who approved the Package. (The 'Submitted To' does not provide the required clarity as that can change over time).
2 - In the 'Migration Package' page, in the 'Approval History' tab, indicate the individuals name who approved the Package. (The 'Submitted To' does not provide the required clarity as that can change over time).
3 - The Execution History page, add a column stating the individuals name who approved the package (Similar to Created By/Executed by).
**Impact:**
_We can't upgrade to the newer version due to the Auditors not satisfied with the Evidence/Ownership of the Approved By item, there's no link to a individual when a Package has been approved. _https://support.cubewise.com/code/pulse/-/issues/4399Pulse 6.3.1 - Approval Workflow (Creator can Deploy Package)2024-02-07T09:39:56ZDonovan AustinPulse 6.3.1 - Approval Workflow (Creator can Deploy Package)**Is your feature request related to a problem? Please describe.**
For SOX, we can't have the Creator of a Migration Package Deploy their own Package (**Even if approved**).
Currently, once a Package is approved, the creator can deploy ...**Is your feature request related to a problem? Please describe.**
For SOX, we can't have the Creator of a Migration Package Deploy their own Package (**Even if approved**).
Currently, once a Package is approved, the creator can deploy the Package.
**Describe the solution you'd like**
Person A - A TM1 Developer and developed a solution to be promoted to PRD.
Person B - A TM1 Developer (Not Person A)
Person C - System Owner/Team Lead/Product Owner (Part of Notification group: Control Owner)
Person A:
Can create Package with ID #00001
Can request approval to Notification Group: Control owner.
Can't approve based on Security Group
**CAN't deploy Package ID #00001 (Whether the Package #00001 is approved or not approved. Author can't deploy their own Package)**
Person B:
Can't approve based on Security Group
Can't deploy package if not Approved.
Once Package ID #00001 is Approved, they can Execute/Deploy Package ID #00001 BECAUSE THEY AREN't the Auther of the Package.
Person C:
Can't create a Package with group Security
Can Approve a Package as they have 'Approve Package' security.
**Describe alternatives you've considered**
Nonavailable, except manual controls.
**Additional context**
Add a config where a creator/author can't deploy a package where they are the creator/author.https://support.cubewise.com/code/pulse/-/issues/4398Pulse 6.3.1 - Rejected Migration Packages should be locked/non-deletable2024-02-01T07:48:07ZDonovan AustinPulse 6.3.1 - Rejected Migration Packages should be locked/non-deletable**Is your feature request related to a problem? Please describe.**
When a Migration Package is REJECTED via the Approval Function, the Package should be Locked (i.e. one should not be able to delete a package once rejected). This is sim...**Is your feature request related to a problem? Please describe.**
When a Migration Package is REJECTED via the Approval Function, the Package should be Locked (i.e. one should not be able to delete a package once rejected). This is similar to a Migration package that has been executed in that one can't then go and delete the Package.
The Auditors always state, that if something is rejected, its not a 'bad' thing, its showing that the process/control works.
**Describe the solution you'd like**
Once a Package is Rejected, the Package should be locked and one should **NOT** be able to delete/change/recreate the Package.
**Describe alternatives you've considered**
We ensure we don't delete a Rejected Package, however the Auditors requires a system based control.https://support.cubewise.com/code/pulse/-/issues/4380Flow Diagrams doesn't include Control Objects2024-01-19T06:20:44ZRupesh KumarFlow Diagrams doesn't include Control ObjectsHi Team - Please confirm if there is an option to include control objects (Element Attribute cubes etc.)while generating flow diagrams, a number of our rules refer element attribute cubes and we would like them to show up in the flow dia...Hi Team - Please confirm if there is an option to include control objects (Element Attribute cubes etc.)while generating flow diagrams, a number of our rules refer element attribute cubes and we would like them to show up in the flow diagram however don't see any option available, refer attached screen-print![Flow_Diagram_Issue](/uploads/29be25a0622e58d9f803be4b961187ee/Flow_Diagram_Issue.png)
Version: 6.2.0https://support.cubewise.com/code/pulse/-/issues/4350Enhancement Request - Pulse maximum concurrent users alert.2023-12-15T11:09:38ZCare BEEnhancement Request - Pulse maximum concurrent users alert.Hello Team, good morning.
We setup an alert for maximum concurrent users. But the alert is triggered by 1 user with multiple sessions. This is probably because of REST API but is there a way to filter unique concurrent users? If so, how...Hello Team, good morning.
We setup an alert for maximum concurrent users. But the alert is triggered by 1 user with multiple sessions. This is probably because of REST API but is there a way to filter unique concurrent users? If so, how can this be done? If not, can it be included in future versions as concurrent users is different than concurrent sessions?
Thanks in advance.
Eloy.https://support.cubewise.com/code/pulse/-/issues/4341I am having issues with the view changes, when I look via migration.2023-12-12T21:03:56ZPeter ChoiI am having issues with the view changes, when I look via migration.> Mark the issue as **Confidential** to keep log files and screenshots private
**1. Key information:**
- Company / Customer Name:
- OS and Version: Windows Server 2016
- TM1/PA Version: 11.
- Pulse Version: 6.3.0
- Browser: Chrome
**2...> Mark the issue as **Confidential** to keep log files and screenshots private
**1. Key information:**
- Company / Customer Name:
- OS and Version: Windows Server 2016
- TM1/PA Version: 11.
- Pulse Version: 6.3.0
- Browser: Chrome
**2. Items to attached**
* [ ] conf\\Pulse.cfg
* [ ] zip the Pulse **logs** folder
* [ ] screenshot of the Status tab in the Pulse About page
* [ ] tm1s.cfg
* [ ] tm1s-log.properties
![image.png](/uploads/fb64183370bdfd4e196981b8f7be2148/image.png)
**3. Describe the bug**
When I go into view change in the the migration screen, I get the following where Pulse does not recognise the carriage return and displays \\r\\n
**4. To Reproduce**
Steps to reproduce the behavior: In migration and I am hot promoting via Pulse.
**5. Expected behavior**
It should display the code in a single line and show the difference per line and not the entire code.
**6. Screenshots**
![image.png](/uploads/6d6ababcc0ab00b8f2357da5baaf4b3d/image.png)https://support.cubewise.com/code/pulse/-/issues/4335Granting Administrative access in Pulse through an AD group2024-01-02T16:18:39ZJanardhan GaddamGranting Administrative access in Pulse through an AD groupHi Team,
We have installed Pulse 6.3.0 and able to see the AD groups to provide the access but able to access for admin we have to check the check box.
Do we provide the admin access through AD group as well? if not what is the ETA t...Hi Team,
We have installed Pulse 6.3.0 and able to see the AD groups to provide the access but able to access for admin we have to check the check box.
Do we provide the admin access through AD group as well? if not what is the ETA to fix the issue.
Regards,
Janardhan Ghttps://support.cubewise.com/code/pulse/-/issues/4316Auto Archive old package when using recreate2023-11-23T11:26:59ZLuke BrownAuto Archive old package when using recreate**Is your feature request related to a problem? Please describe.**
When using the pulse migration package re-create function the old package is left on the active packages screen, this creates over time a long and sometimes confusing li...**Is your feature request related to a problem? Please describe.**
When using the pulse migration package re-create function the old package is left on the active packages screen, this creates over time a long and sometimes confusing list which can beg the question, which is the right package.
**Describe the solution you'd like**
It would be great if when using the recreate option the old package is automatically Archived, meaning we can access the old package if needed but the latest version is always the one shown on the main packages screen.
**Describe alternatives you've considered**
NA
**Additional context**
NAhttps://support.cubewise.com/code/pulse/-/issues/4298PULSE: Indicate/Config per Pulse Instance TO WHICH instances one can deploy2023-11-08T06:12:29ZDonovan AustinPULSE: Indicate/Config per Pulse Instance TO WHICH instances one can deploy**Is your feature request related to a problem? Please describe.**
We have a DEV Pulse Instance and a PRD Pulse Instance do comply with SOX/Audit Controls
We are allowed to on:
- On DEV Pulse Instance to migrate: DEV to DEV / DEV to UAT...**Is your feature request related to a problem? Please describe.**
We have a DEV Pulse Instance and a PRD Pulse Instance do comply with SOX/Audit Controls
We are allowed to on:
- On DEV Pulse Instance to migrate: DEV to DEV / DEV to UAT / PRD to UAT / PRD to DEV
- On PRD Pulse Instance to migrate: DEV to *PRD* / UAT to *PRD*
We are required to prove to the Auditors that our DEV Pulse Env can't Deploy TO PRD (However we need to use it to PULL from PRD to DEV/UAT, so it needs access to PRD but should not be allowed to PUSH)
**Describe the solution you'd like**
Per Pulse Instance, per model config (Where you specify Username & Password etc) have a tick box indicating if you can deploy TO that instance.
Meaning, in DEV Pulse all DEV & UAT TM1 Instances will have the Deploy TO Ticket (Yes) but the PRD TM1 Instance won't have it Ticked (No).
In PRD Pulse we will have only PRD TM1 instance Deployment Ticked (Yes) and all other env will have it set as No.
Its a similar Lookup config/check as the Approval but on a Target TM1 Instance level.
**Describe alternatives you've considered**
We will try to have our DEV Pulse only have READ Access to PRD TM1 Instance to see if that works (i.e. should be able to read existing objects but not overwrite), however that will cause our DEV Pulse not to see logs/threads etc of PRD TM1 Instance.
**Additional context**
Add any other context or screenshots about the feature request here.https://support.cubewise.com/code/pulse/-/issues/4288Pulse Packages Dashboard (Execution Date with possible filter and Export to C...2023-11-29T04:56:44ZDonovan AustinPulse Packages Dashboard (Execution Date with possible filter and Export to CSV Function for SOX/Audit)**Is your feature request related to a problem? Please describe.**
a Few enhancement requests:
1- The From and To Columns in the Migration Packages page does not add any value, can there be a filter of applicable columns similar to the ...**Is your feature request related to a problem? Please describe.**
a Few enhancement requests:
1- The From and To Columns in the Migration Packages page does not add any value, can there be a filter of applicable columns similar to the Live monitor Sessions Monitor?
2- There's no way of identifying which Packages were EXECUTED ON X DATE on the Migration Packages page. Meaning the Auditors can't identify which of the listed Packages should be under our Change management review for Q3. We need to open each and every package one by one to identify the EXECUTED Date.
3- There's no Export Function in the Migration Packages page to CSV, this is a vital step to any Audit/SOX Process where screenshots need to match an export (Preferably with a Filter Option, i.e Executed To Instance ABC and between X and Y Dates)
**Describe the solution you'd like**
1- Columns Filter (on/off or X tick and Yes Tick) for the Migration Packages Page to only show whats relevant to us.
2- A field indicating the date the package was last executed and to which target instance.
3- An Export function to dump all the Packages (Not detail) to csv like any Ticketing System can do.
**Describe alternatives you've considered**
1- No alternative
2- Taking multiple screenshots of unrelated packages within the package (Detail) to proof to the Auditors these packages aren't relevant
3- Copy screen and past to excel.
**Additional context**
This request can possibly be merged with: https://support.cubewise.com/code/pulse/-/issues/4275https://support.cubewise.com/code/pulse/-/issues/4268Migration - Add the approver name into the Approval History panel.2023-10-17T08:15:45ZVincentMigration - Add the approver name into the Approval History panel.Hi,
I'm using Pulse 6.3.0 and I can't find a way to see from Pulse who approved my request:
![image](/uploads/077b30dbd6f5214ed569512aa2ef72ff/image.png)
I can only see when it was approved.
Could you please add the name of the appro...Hi,
I'm using Pulse 6.3.0 and I can't find a way to see from Pulse who approved my request:
![image](/uploads/077b30dbd6f5214ed569512aa2ef72ff/image.png)
I can only see when it was approved.
Could you please add the name of the approver into the Approval History section?
Cheers,
Vincenthttps://support.cubewise.com/code/pulse/-/issues/4267Migration - Add url to the approval page in the email.2023-10-17T08:11:31ZVincentMigration - Add url to the approval page in the email.Hi,
I'm using Pulse v6.3.0, please find below a screenshot of the email received after someone created an approval request:
![image](/uploads/1f5f95e33bcc0bcd5998cf2585ced373/image.png)
It would be very handy to have a link in the ema...Hi,
I'm using Pulse v6.3.0, please find below a screenshot of the email received after someone created an approval request:
![image](/uploads/1f5f95e33bcc0bcd5998cf2585ced373/image.png)
It would be very handy to have a link in the email to open the approval requests page: pulseURL#/packages/approval
In the email it would be also nice to see the Author of the request.
From the email, we can't see who made this request.
Cheers,
Vincenthttps://support.cubewise.com/code/pulse/-/issues/4256User should be able to delete multiple alerts.2023-12-05T11:38:17ZJohnson AbrahamUser should be able to delete multiple alerts.Currently user can delete only one alert at a time.
It should be possible to delete multiple alerts.Currently user can delete only one alert at a time.
It should be possible to delete multiple alerts.Johnson AbrahamJohnson Abrahamhttps://support.cubewise.com/code/pulse/-/issues/4197Change the retention period for a specific index2023-09-20T11:27:43ZMatthieu RedouinChange the retention period for a specific indexThe retention period of Elasticsearch indices is bound to their frequency.
So it means that all monthly indices (which is the most common frequency) have the same retention period.
Is it possible to configure a different retention period...The retention period of Elasticsearch indices is bound to their frequency.
So it means that all monthly indices (which is the most common frequency) have the same retention period.
Is it possible to configure a different retention period by index.
Example:
| Index Name | Index Frequency | Retention Period |
| ------ | ------ | ------ |
| pulse-chore-process-history | Monthly | 2 months |
| pulse-tm1-object-history | Monthly | 6 months |Elias GonzalezElias Gonzalez