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.
Jim Pfleger suggested an idea (#1706) · Jun 29, 2017 at 06:42 PM · administrationcloudshelllogs
We need best practices or a mechanism for automated monitoring of the CloudShell infrastructure. While the CloudShell Monitor is a good tool for looking at logs and alerts interactively, there is no way to feed anything from it into a proper monitoring tool that can generate alerts, keep a history, etc.
I think there are a few ways this can go. One is to make a CloudShell Monitor service, with a REST API. Other monitoring systems could query the API for events and metrics.
Another option is for Quali to publish best practices on monitoring the CS infrastructure. These would include:
Data Dog has a good summary of effective monitoring.
There is a third option, which I only mention here because I don't like it and want to explain why, and that is for Quali to provide a closed, preconfigured monitoring system with the product. I think this would be difficult to implement in a way that accounts for all the deployable architectures, and it would lock both Quali and its customers into a single platform. Also, doing this instead of exposing data and logs goes against the openness that makes CloudShell such a powerful solution.
Maya Ber commented · Jul 10, 2017 at 07:37 AM
Hi. Thanks for the idea. Providing monitoring best practices is something that we would like to do in the future. Initially we would like to start a discussion on this in our community administrators forum.
Maya Ber commented · Jul 18, 2017 at 09:27 AM
Hi @jimpflegervz, please see discussion here, started by our own team that uses CloudShell internally:
http://community.quali.com/content/kbentry/1750/cloudshell-monitoring-best-practices.html
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.
Add "CreateDate" field to the Resource Manager-Users view
Domain admins need the ability to create and connect resources in their own domains
Admin level control to create a scheduling Blackout/Service Period
Ability to manage Abstract templates between Domains
Email notification for all users or a group of users when Setting up a future maintenance window
Permitted Users on reservations that exceed their current permissions
Exclude Inventory from CloudShell portal
Allow Cloud Provider Shell to define default App Shell Template
Gen2 Service Shells need to be able to managed by Categories
Ability to disable QualiX connection options at a device level