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 >.
Hi All,
I am developing a CloudShell service for Wireshark. The idea is that you will be able to record and analyse packet traffic on virtual and physical resource interfaces within an active sandbox.
One issue I have is that long after I cancel a Service command, the messages still keep appearing in the Output window (I use the CloudShell API "WriteMessageToReservationOutput" command). I am currently printing out a message for every captured packet so how do I force the pending messages to be flushed faster?
Also, this begs the question of whether this is best practice? Should I build a complete response for the Service command and use the return option to print the output in one message.? Should I do the same for the complete response with the API? This has the benefit of not clogging the activity feed with 100's if not 1,000's of messages but it has the downside of the user having to wait until the command to complete until they see anything.
Any thoughts?
Thanks
Gary
Answer by Yaniv Kalsky · Apr 04, 2019 at 04:40 PM
Hi @Gary.W
While it might be nice to see the messages in the output window, you also need to be aware of these messages stored in the DB, so I'm not sure if that's something you'll want to have for the long run.
You can maybe just report some progress while the command runs, but at the end upload a file as an attachment to the reservation (which also stored in the db - but can be removed on teardown if not really needed).
Yaniv
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.