Azure Monitor-Log Analytics
Welcome to the "Azure Log Analytics ":https://azure.microsoft.com/en-us/services/log-analytics/ Feedback page. We appreciate your feedback and look forward to hearing from you. Use this site for new ideas and bug reports or to request help.
NOTE – Log Analytics is now a part of Operations Management Suite. Learn more at http://microsoft.com/OMS
- For general discussion/question and answers (not ideas and bug reports) use the MSDN Forum
- Onboarding issues? Read this troubleshooting guide
- How do I do XYZ? Try our documentation
- Customers with Premier support can log support cases via Premier
- Customers with Azure support agreements can log support cases in the Azure portal
-
Service Map support on Ubuntu
Ability to install the Dependency Agent on Ubuntu
501 votes -
Add the ability to export the server listing (to excel, text file, etc.) which could then be used for internal asset management comparisons
Add the ability to export the server listing (to excel, text file, etc.) which could then be used for internal asset management comparisons. We could use this export against the Security Map export to validate server missing. Would also allow us to compare that export with an internal Asset Management inventory list to find deltas in machines not having the Dependency agent installed. we have a large organization (3,500+ servers) and we want to make sure all servers get the Monitoring and dependency agent.
33 votesYou can build a query and export its results to XLSX. You can automate this.
-
Service Map available in Europe
Make Service Map available for Europe region.
25 votesWe are excited to announce that we deployed Service Map to the West Europe region ahead of schedule.
-
Reduce Service Map inital load time by not default displaying service map of first server in list.
On entering the Service Map solution you have to wait for the Loading Map Data message to disappear before you can start to use the Filter field. This can make you wait 20-30 seconds to render a service map for a server that you're not interested in.
Would be nicer to drop start to a quick loading Service Map overview screen or just not render anything.
3 votesWe have changed the behavior so Service Map no longer loads the first machine by default. In addition, we have made several improvements to overall map load time and navigation once the map is loaded.
-
Dependency agent forces reboot
Installing the Service mapping dependency agent may cause the computer to spontaneously to reboot. A note or warning to this effect would be welcome.
1 voteThe latest version of our agent (9.0.3 or later) has this fix in it. Our agent will not force a reboot, but there is a new flag you can set if you WANT it to reboot if necessary (only necessary if there are locked files).
-
DNS resolution of Service Mapping clients
It would be useful if IP addresses of back-end machines and front-end clients without agents were resolved in DNS. Presently these nodes are shown as plain IP addresses.
Preferably the DNS lookup should be performed on the Dependency agent.
1 voteThis feature has shipped for back-end dependencies that don’t have a agent.
-
Map too large to display
When Map too large to display allow to select less services connection to display or display list mode
1 voteYesterday we checked in the new feature to group connections to back-end machines that don’t have an agent by port, and increased the threshold for the number of nodes and edges maps can render.
This feature will allow you to display much more complex maps, and provides a new capability to understand the nature of the connections from the focused machine to back-ends without an agent.
We will continue to invest in ways to filter and simplify maps, but this should address any maps you have that weren’t rendering previously.
- Don't see your idea?