Hi all. I have been trying to get my security team to allow us to join the preview, however they have been pushing back. Is there a way to control users' ability to only view data from inside the corporate network? I.e. not over the web.
Also, within the product, can you give role based access, e.g. application teams only have access to app data etc?49 votes
Operations Management Suite Agent for Linux Public Preview (2016-01) work fine with an IPV4 proxy address but not work with an IPV6 proxy address.
Error with IPV6 address on proxy.conf:
[error]: Failed to parse the proxy configuration in '/etc/opt/microsoft/omsagent/conf/proxy.conf'19 votes
We are working to ensure that Proxy Configs will work with IPv6
Backup Workspace settings, dashboard, saved queries, and configuration - and be able to restore to a new workspace.
Would help if configuration ever gets lost, corrupt, or we want to recreate a new workspace and keep some favorite settings.16 votes
I would like be able to have a consolidated view over one o more workspaces. Consider a multinational organization with local IT running different parts of the infrastructure and a consolidated view for central analysis.16 votes
20 Custom fields too little. I am sure you can increase the quota from 20 to 200 without a sweat :)8 votes
We’re closely monitoring telemetry for Custom Fields which is currently in a public preview. We’re planning on increasing the quota depending on customer need at this time.
Need more status update than "let it run overnight" "wait several hours". It would be great to get additional status. For example: we've successfully connected to your onpremise System Center server. OR you need to setup a connection before we can pull data. OR we're currently pulling data (1GB out of 10GB).7 votes
There are a few different requirements and different things that can happen for each intelligence pack. Some of that troubleshooting needs to be done on-premises (the service doesn’t know what it has never seen…). Refer to our troubleshooting blog post for the latest http://blogs.technet.com/b/momteam/archive/2014/05/29/advisor-error-3000-unable-to-register-to-the-advisor-service-amp-onboarding-troubleshooting-steps.aspx
Nevertheless, onboarding has been greatly simplified (a few times, leading to GA of the service) in the last year, including the introduction of the ‘Settings’ tile (hub), and the scale of the service has improved to deal with higher data rates (not making you wait too long, basically, see this http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6519343-real-time-near-realtime-data-collection ).
We think we are in a much better place than when you filed this idea, do you agree?
There should be a way to restrict a single user to only be able to see the log files from a single computer group.6 votes
We do plan to evolve the access model in Log Analytics so users will be able to see logs based on permissions. We will use a slightly different model from the one proposed here but the principal is that users will see only logs from machines that they are permissioned to.
The current user should be listed on the top right bar along with the ability to log out. It is not important to display the Data Plan.2 votes
As part of our integration with the Azure portal, you’ll see your user listed in the top of the portal
Allow Performance Counters to be copied across workspaces. This would allow performance counters to be created and validated in a dev workspace and copied to a production workspace.
The experience would be similar to reading and saving Saved Queries and Computer Groups.2 votes
We’re working towards having all configuration to be done via API, which will enable scenarios such as this.
tooltips on the icons in the top right menu (settings, help, feedback, etc.)1 vote
Thanks for your feedback, we will address it.
- Don't see your idea?