Azure Storage is actively working on features that could improve the migration story from standard to premium disks.
This is an interesting idea, though not feasible at the moment. We will leave this on the roadmap to review later on.
What issue are you trying to solve? What use case would this be used for?
It seems to me that placing a restart option on the plan level might do more harm than good, by resetting the memory on all the apps under the plan. Depending on your scenario, auto-heal would be a great solution to solve individual machine issues. See a video by my colleagues here for more details: https://channel9.msdn.com/Series/Windows-Azure-Web-Sites-Tutorials/Auto-Healing-an-Azure-App-Service
Placing this idea under review for now until I understand what’s at the base of the request here.
We haven’t forgotten about this request! This is something we would like to bring in the future, but we cannot provide a timeline at this time.
Thank you for using UserVoice!
This feature is currently in active development. We will update this item to complete once it has shipped so those voting/commenting will be notified.
Thank you for your patience.
Just to provide an update, we are close to launching a private preview. We are in the final testing stages for this feature. We will have another update in the next few weeks with instructions on how to join the private preview.
This is not currently on our road map. However, we will look at this in our next feature review and will provide update on status.
Thank you.Tommy Egeberg shared this idea ·
19 votes1 comment · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →
We are doing work on at the moment on custom fields – http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6519270-support-regular-expressions-regex-or-xpath-to-pe – which represents a stepping stone to allow custom data types into the system.
The first iteration will only extract new (per tenant) fields for existing types, but later we need to address also the collection/gathering aspect (i.e. is your custom data already in azure? http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/7928931-collect-data-from-custom-containers-in-storage-acc or is your data something that comes from an existing log – http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/7113030-collect-text-log-files) to allow customers to define what logs you want, where they are, how do they look, how to parse them, etc.
Basically, we might or might not address this item as an out of the box ‘solution’ but the current thinking is to leave it open until the generic platform capabilities can support it (this and any other logs, at that point).
7 votes1 comment · Azure Monitor-Log Analytics » Workspace Settings / Administration · Flag idea as inappropriate… · Admin →
Yes this is something on our radar that we would like to enable in the future but has not been prioritized yet.