Daniele
My feedback
-
3 votesDaniele
shared this idea
·
-
21 votes1 comment · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →Daniele
shared this idea
·
-
15 votes
This is something we can look at in the future. Thanks for the feedback and we will update once we determine the best approach here.
Daniele
shared this idea
·
-
1 voteDaniele
shared this idea
·
-
10 votes3 comments · Azure Monitor-Log Analytics » Search UI and Language · Flag idea as inappropriate… · Admin →Daniele
shared this idea
·
-
9 votesDaniele
shared this idea
·
-
15 votes2 comments · Azure Monitor-Log Analytics » Alert Management Solution · Flag idea as inappropriate… · Admin →
We have rolled out in public preview, enhanced alert interface allowing alert owners to acknowledge or close alerts. See: https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-overview-unified-alerts#enhanced-unified-alerts-public-preview
An error occurred while saving the comment -
3 votes
Are you still having this issue? I am unable to reproduce this issue in the edge browser now and can successfully start both test and published runbooks.
If you are still experiencing the same problem, can you please provide more detail.
An error occurred while saving the comment Daniele
commented
Hi Beth, you're right with the current build of edge (25.10586.0.0) the issue is not there anymore. I should have closed the issue myself, sorry.
Ciao
DanieleDaniele
shared this idea
·
-
4 votesDaniele
shared this idea
·
-
8 votes
Proxy support is now available for PowerShell script runbooks. PowerShell Workflow Runbooks will be targeted next.
Daniele
shared this idea
·
-
7 votes
we are understanding the requirements here and when we plan it, will let you know.
Daniele
shared this idea
·
-
40 votes
Thanks for the idea, Daniele.
What would be the purpose of having such information? What would be the use cases of such information when the user is unable to revert the changes?
An error occurred while saving the comment Daniele
commented
The goal is to able to understand if an issue root cause can be related to a newly released MP. Take for example the issues we're facing with the latest wire data MP, it took some time to correlate the CPU spikes with the MP release. Let's say I have my CPU perf in OpInsights and I can see when the spike started, then I can time window into change tracking and see what's happened. 2' and I have a possible cause across al my systems.
On the other hand, you're right I cannot do anything except open a support call, and this is anothjer topic I'm going to post: give us the ability to revert to a last known good configuration, or stage updates. Today I had to remove the WireData MP that was killing the DCs, this has been possibile since we're just evaluating the module, but if it happens once in full production? Not a good situation to be in, for the customer and for OpInsights credibility. OpInsights is susceptible to bad MPs as SCOM is, the difference is with SCOM I can always revert, I can have a staged process, multiple MGs, in a way or another I'm able to limit the damage.Daniele
shared this idea
·
-
3 votes2 comments · Azure Monitor-Log Analytics » Wire Data Solution · Flag idea as inappropriate… · Admin →
The new wiredata solution is currently in private preview.
Daniele
shared this idea
·
-
7 votesunder review · 0 comments · System Center Data Protection Manager · Flag idea as inappropriate… · Admin →Daniele
supported this idea
·
-
14 votesunder review · 1 comment · System Center Data Protection Manager · Flag idea as inappropriate… · Admin →Daniele
supported this idea
·
-
17 votesDaniele
supported this idea
·
-
17 votesDaniele
shared this idea
·
-
1,986 votesDaniele
supported this idea
·
-
573 votes
Update: We are currently working on enabling operational backup for blobs and the ETA for the limited preview is November ’20.
Do check out this short demo to catch a glimpse of what operational backup of blobs will offer: https://aka.ms/AB-BlobBackup
For more details, please reach out to us at AskAzureBackupTeam@microsoft.com
Daniele
supported this idea
·
-
72 votes
Great feedback. We are looking at potentially delivering a solution in this area. Thank you!
Daniele
shared this idea
·
We would need for analysis puposes Site Name and TicketId as well.