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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow a Kusto query to reveal update agent readiness and the compliance state for patch management / azure automation

    I would like to determine if we have machines that aren't reporting a ready state due to issue with monitoring agent or hybrid workers.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Shared query link

    Log analytical query “ share link once opened goes to Getting Started page and until we click getting started button query explorer does not run the query. Is there a way to skip the getting started page when using link shared for query?

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Incorrect response codes in Log Analytics for WordPress apps hosted in App Service

    We have a couple WordPress apps hosted in an Azure App Service and MySQL database. We've enabled Application Insights which does capture some information that can be useful.

    Upon building dashboards with this data, we've noticed all the http response codes collected are 200 even though in the raw logs some responses are 404 (page not found). This makes the information when attempting to build useful dashboards invalid and/or inconsistent when we want to capture failures.

    Support ticket was raised but advised WordPress and App Insights is not supported. Please either remove the option for the plugin or provide support…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback and its now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  4. Add the Continous Export function to Log Analytics (as seen in Application Insights) or provide similar functionality

    Still not quite at feature parity between Application Insights and Log Analytics. Both can now set the retention period to 730 days - but if you need to store logs for longer, only Application Insights has a function to do this via Continous Export.

    Ideally, we want to be able to long-term store logs for more than 730 days. We don't necessarily need the analytics aspect, so archive/cold storage in a storage account (or the like) would be perfectly fine over increasing the retention period past 730 days.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback and its now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  5. Option to select Resource-Specific with CLI, PowerShell and Rest API for collect resources logs

    Please add an option to select Resource-Specific with CLI, PowerShell and Rest API for collect resources logs.
    The documentation https://docs.microsoft.com/en-us/azure/azure-monitor/platform/resource-logs-collect-workspace#select-the-collection-mode shows it's currently not possible to select this destination with a script. So all logs will be stored by default to AzureDiagnostics and we can face some limits with the number of columns of the table.
    It's also recommended by Microsoft to select Resource-Specific target tables, but in our context, we need to be able to do it in an automated fashion. Thanks

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  6. View surrounding logs

    Kibana has an amazing feature, where you can view surrounding logs to the current log that you are investigating.
    Could we get this in Log Analytics.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  7. Allow adding custom AD user attributes for AD and Sharepoint Analytics

    We have attributes like Market ID per user , synced to Azure.
    Custom user attributes should be possible to sync to Analytics so you can use for queries , usage reports and so on.
    If not in you have to build a second loop, identify user, identify user related custom attribute , a mess for large tenants.
    At the end the same for the other integrations like Exchange, Sharepoint Analytics required

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  8. Multiline log support

    It is very inconvenient when the log comes separately from the stack trace messages, the order of the lines is mixed. This needs to be fixed. Ideally, everything should come in one message in multi lines

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Download log analytics chart report in PDF format

    log analytics feature we cant save the chart and graph as pdf format

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  10. Currently the JSON log messages getting truncated and split inot multiple lines when its very long

    Currently we are facing an issue while analysing application logs. When the JSON log message is very long its getting into multiple lines. Our requirement is to get them in one line. Could you please help us fix this issue? Please let me know if you need any further informations?

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Log Analytics agent support for specific event IDs

    I'd like to be able to ingest specific Windows event log event IDs. Considering billing is done by ingestion, there are some Informational events I need to ingest while ignoring other, extremely noisy events. In my opinion, there should be more than an "all or nothing" configuration approach.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  12. Why Does MS Continuously Break Things that Work???

    I have Azure Functions. For certain operations, during development, I use context.getLogger().severe(logMessage); Simple. Straightforward. AppInsights, as piggish as it was, would at least show the message by default. I did not have to learn yet another bit of syntax that is almost but not quite like some other logging syntax. Now, I look at Log Analytics (something wrong with AppInsights as a name? Who could guess) and I get a bunch of useless IDs, but DO NOT GET THE LOG MESSAGE by default. OR THE SEVERITY. Supposedly a field called 'desc' should be in the result (is that the log…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Log Management and Log Collection Policy  ·  Flag idea as inappropriate…  ·  Admin →
  13. Ability to see what resources support Resource-Specific Diagnostics

    Currently we aren't able to determine which resources support Resource-Specific Collection Mode. It is buried in the documentation for each resource: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/resource-logs-collect-workspace It would be gratefully beneficial to have a complete list seeing Microsoft is recommending users to switch to this mode for their resources where applicable due to the 500 field limit on the AzureDiagnostic Table

    33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. App Insights should have the capability to have a logarithmic chart.

    When capturing stats against the 95/99th percentile latencies, it would be useful to have the ability to apply a logarithmic chart to App Insights. Currently, this can be completed in Splunk.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for the feedback. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  15. custom logs timestamp

    Please add this timestamp delimiter YYYY-M-D HH:mm:ss.

    Currently have logs in an application that use this and would like to gather the custom logs using this delimiter format.

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for the feedback. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  16. Please DO NOT RETIRE the demo site: https://portal.loganalytics.io/demo#/query/main

    For log analytics, there is a demo site: https://portal.loganalytics.io/demo#/query/main, which is very useful for testing purpose since it has a lot of data.

    And now I see it will be retired on September 2nd, 2019, please keep it alive.

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Log analytics to support multi dimensional metrics input from Event Hubs

    Sending multi-dimensional metrics via diagnostic settings is not currently supported. Metrics with dimensions are exported as flattened single dimensional metrics, aggregated across dimension values.
    For example: The 'Incoming Messages' metric on an Event Hub can be explored and charted on a per queue level. However, when exported via diagnostic settings the metric will be represented as all incoming messages across all queues in the Event Hub.

    The Diagnostics and Metrics team did confirm that the Incoming messages metric is multi-dimensional. And because of this when sending the data to Log Analytics it will only present all of the incoming messages…

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for the feedback . Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  18. Support millisecond/microsecond precision for time-generated-field in HTTP Data Collector

    Support millisecond/microsecond precision for time-generated-field in HTTP Data Collector. Use ISO 8601 format YYYY-MM-DDThh:mm:ss.msecZ

    66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for the feedback. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  19. Include "Valued caching policies" on the analytics result

    It would be very helpful if you have a built-in mechanism for counting value cache misses/success.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for your feedback. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  20. No AzureActiveDirectory audit data in workspace after recreating ws with same name

    AAD diagnostic Settings do not update the id of the Workspace if this newly created one gets the same name again.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for the feedback. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

← Previous 1 3 4 5 6 7
  • Don't see your idea?

Feedback and Knowledge Base