These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
VISIT OUR DIFFERENT FORUMS:
Announcements > | |
CloudShell > | TestShell > |
Developers > | BI (Business Inteligence) > |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide > | Configuration Management > |
Getting started with Shells > | Extending CloudShell with Cloud Providers > |
Getting started with Orchestration > | API Guide > |
To share your integration, follow the instructions in this guide >.
Richard Hill suggested an idea (#5413) · Jun 07, 2021 at 03:11 PM · servicelogsquali servercloudshell
There is a known issue in 9.3 (fixed in patch6) where the Quali.DB fails to update the QualIInsight.DB. and once this failure starts, it does not self-correct over time. While correctable, this kind of SQL error is NOT alerted either in the SQL logs nor in the Quali Admin's portal so you find out about it when failures are obvious and data is missing.
There should be an alert sent to the Quali Admin(s) Cloudshell environment when this failure, or that of any other background process, fails so that we know about it as it has happened, especially that critical data update process. It would not be a lot of new code to alert on a failure vs constant alerts that things are working. (Fewer pop-ups are good)
This may have been discussed in another entry but I cannot find one - so I have created this.
gilat naor commented · Sep 01, 2021 at 06:22 AM
Hi @Richard Hill, sorry for the delay, can you please explain what type of update fails – on nightly, on reserve, etc? did you open a ticket about it? if not - please do,
Richard Hill commented · Sep 03, 2021 at 01:50 PM
Gilat
This was entered as ticket #45111 opened on 5/26/2021 and closed on 6/17/2021
It was originally assumed to be another of the many Sisense issues we have had over the years but it turned out to be an intermittent bug that occurred after a Schema change back in 9.3. which was fixed in patch6, The defect is that the Quali.DB suddenly fails to update the QualIInsight.DB. and once this failure occurs, it does not self-correct over time.
We applied patch6 and then also found that the 9.3P6 upgrade is different from the previous ones in that it does not CALL the configuration applets when it does configuration, so we had to run the QualiConfig applet afterwards.
Due to the fact that we had assumed a Sisense issue at first, we had created new databases (after renaming the originals to no avail), and that was the last piece of fixing the issue as we had to re-associate the Elasticube to the correct databases.
This request is that additional code be added in the next patch for 9.3 as well as your current releases so that a nightly check on Quali background processes is done so that if any of the below occur, an alert is generated and sent to the admin accounts in Quali and Sisense and if a SQL process is involved, that the error be written to the log file of the running SQL process. This would not actually fix anything but would give next-day awareness, at the wors,t instead of discovering (in the case of my ticket) it days or weeks after the failure. This would provide greater awareness failures in the Quali data collection and presentation into Insight.
* "QualiInsight.db" (or whatever name has been assigned/changed) is not updated from the "Quali.db" (or whatever name has been assigned/changed)
* Elasticube rebuild fails to complete at any scheduled rebuild
* Elasticube cannot link to the QualiInsight.db (or whatever name has been assigned/changed)
It would also be great to have a process where the Elasticubes of record and the three SQL databases were backed up nightly or weekly automatically - but this is if lessor importance.
Thank you
These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
Announcements | |
CloudShell | TestShell |
Developers | BI (Business Inteligence) |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide | Configuration Management |
Getting started with Shells | Extending CloudShell with Cloud Providers |
Getting started with Orchestration | API Guide |
To share your integration, follow the instructions in this guide.
Help us make things better. Share your great idea or vote for other people's.
Quali Team server Logs tagged with originating sandbox id
Gen2 Service Shells need to be able to managed by Categories
Service links to remain available after the reservation completed
Capability to exclude services
Wizard for easy upload of logs to Quali FTP server
Instruction panel width control request