Darren
My feedback
-
1,527 votes
At this point our recommendation is to move resources into a new Resource Group with the new name.
Darren
supported this idea
·
-
185 votes
We continue to investigate this. Due to the current roadmap and strategy this will remain in our backlog. Please continue to share feedback related to this topic to help us make an informed decision at a later time.
Darren
supported this idea
·
-
65 votes4 comments · Azure Monitor-Log Analytics » Agent Management (OnPrem components) / Connectivity / Setup · Flag idea as inappropriate… · Admin →
We support multi-homing for Windows agents:
https://blogs.technet.microsoft.com/msoms/2016/05/26/oms-log-analytics-agent-multi-homing-support/We are working on multihoming for Linux agents.
We are also working on support for multihoming with the Azure VM extension
Darren
shared this idea
·
-
39 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?
Darren
supported this idea
·
-
5 votes1 comment · Azure Monitor-Log Analytics » Security and Audit Solution · Flag idea as inappropriate… · Admin →
Will forward to the team to see if that field can be enabled as facetable.
ThanksDarren
commented
Hi. Any update with this?
Darren
shared this idea
·
-
18 votes4 comments · Azure Monitor-Log Analytics » Solutions / Packs Gallery and new IP ideas · Flag idea as inappropriate… · Admin →
We do multiple deployments a day, this is very challenging to do in a services world, especially for the cloud part: the portal and multiple other parts of the online service can change and be redeployed dozens of times each day, every day, on a typical week when developers check in new code, this goes thru a bunch of automated validation, and then gets pushed out.
We have ability to show/hide new features to selected tenants/workspaces – but there are a lot of teams that independently contribute to the portal and system for various scenarios, and check in and deploy their changes independently thru automated workflows.We intentionally go ‘slower’ with the Intelligence Packs – because we know that they can affect on-premises. Those are generally pushed out at a slower cadence, but can still happen a few different times in the same week; the deployment mechanisms are similar, but…
Darren
commented
I've put together this script to give some visibility on management pack updates pushed out from OMS into SCOM.
http://twomonkeymonsters.joyce.net.nz/2015/07/alerting-on-oms-solution-pack-update.html
Darren
commented
Unfortunately, we don't have a test system with all our production servers (around 300) due to resourcing, and multihoming all SCOM agents to both test and prod could cause other issues. Our test setup is relatively small and we add agents as needed for test purposes.
Also to have a test environment - this means running two Ops Insights instances - one prod and one test.A blinking tile would be good, but that means staying signed in - and we may not have the console visible at all times.
A feed is ideal. Even if it doesn't include a changelog, just a notification that xyz has been updated. Short notice is fine - any notice is better than no notice. Even if it's done as the same time as the update.
An example is the recent issue with an IP update for Microsoft.IntelligencePacks.Types.HealthServiceProxyConfiguration that incorrectly flagged as a system rule. This broke monitoring in SCOM on our 2003 servers that didn't have powershell. As I was unaware of an IP update we ended up escalating to Premier Support, as I was not aware of any changes that may affect our environment.
It would be awesome if you guys could add this feature.
Darren
shared this idea
·
-
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.
Darren
shared this idea
·
-
14 votes2 comments · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →
In the future we will work on plans for higher retention policy.
For the ‘export’ functionality, you might want to check the API idea http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6519057-programmatically-submit-search-requests-and-receiv but, realistically, after you uploaded terabytes of data over a few months time… even the concept of downloading everything back at that point seems daunting.
Darren
commented
Another idea would be is possible for the Ops Insights Agent / SCOM agent to first put the logs on a onpremise server before shipping them up to Azure. Means there is always long term on-premise copies for archival purposes.
Darren
shared this idea
·
-
13 votes2 comments · Azure Monitor-Log Analytics » Extensibility / Partner scenarios · Flag idea as inappropriate… · Admin →
Thanks for the feedback.
A starting point you could look at in this sense is the opsmgr dashboard integration, which is script-based (so, easy to dissect and recompose – it shows you how to issue your own search to the portal’s search page programmatically) http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6519195-integrate-search-into-opsmgr-dashboards
or today you can run your own code – the recently released Search API http://blogs.technet.com/b/momteam/archive/2015/06/18/oms-log-search-api-documentation-is-here.aspx
—
Also look at this other – related, more generic – idea http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6984082-access-read-only-dashboard-directly-from-url
Darren
commented
Thanks for that. I just had a quick look. It appears to be more for search-based stuff. I want to put the big widgets on the home page on the sharepoint site (eg, Malware assessment pie graph, etc).
Darren
shared this idea
·
YES!