5 votes0 comments · Azure Monitor-Log Analytics » Search UI and Language · Flag idea as inappropriate… · Admin →
Thanks for offering this feature. Currently the plan is to upgrade the portal with many new features, the timeline is being re-designed as part of it.
Until that, I can only recommend you to use the query to generate charts that describe this in the manner that fits your data best.
We’ve recently upgraded the query language. Here’s an example of the new syntax, using 3-hour bins over the last two days of events:
| where TimeGenerated > now(-2d)
| summarize count() by bin(TimeGenerated, 3h)
| render timechart
This is in our backlog. We will update as we make progress on the feature request.
9 votes0 comments · Azure Monitor-Log Analytics » Agent Management, Data Metering and Usage (Portal) · Flag idea as inappropriate… · Admin →
Real-time cleanup would be expensive in the current architecture. When you close the account, data isn’t deleted immediately, but within several days (detailed in the terms of service and/or privacy statement), as part of grooming.
Right now you’d have to close and re-open account for this.
Anyhow I am leaving the idea open, but we feel that at this point this is a ‘nice to have’ – not a critical one – and would take many cycles and resources from doing much higher priority work.
7 votes0 comments · Azure Monitor-Log Analytics » Workspace Settings / Administration · Flag idea as inappropriate… · Admin →
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?
10 votes1 comment · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →
Not our immediate priority, as we as focusing more on operational insights, not business ones.
For merging with non-machine, non-operational data we think the place directionally could be PowerBI – check the idea of providing a ‘connector’ to it http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6519374-integrate-with-powerbi-allow-to-query-and-refres
we are investigating overall noise-reduction techniques for change-tracking. This remains in our product backlog.
27 votes0 comments · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →
Windows Server 2003 and before were using TEXT log files http://support.microsoft.com/kb/168801
Windows Server 2008 and beyond use ETL traces – http://blogs.msdn.com/b/clustering/archive/2008/09/24/8962934.aspx
Also refer to these generic ideas:
Text log files collection tracked here http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/7113030-collect-text-log-files
Collection of ETW traces is tracked here http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6691402-collect-etw-trace-logs
367 votes22 comments · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →
This is currently under development, scheduled to be in preview later in 2018Daniele Muscetta shared this idea ·