Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

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. Situs togel online terpercaya Deposit Termurah Di Indonesia

    Situs togel online terpercaya Deposit Termurah Di Indonesia tahun 2020 http://199.188.201.60/ - comsolindia Adalah Blog Resmi Dari Unsurtoto yang merupakan Situs togel Online terpercaya dengan Deposit termurah 10rb yang paling populer di Tahun 2020

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Multiple data destinations for Linux agent

    The Windows agent can be multihomed to send data to multiple Log Analytics workspaces. The Linux agent can send to only a single destination, either a workspace or management group. It would be a great enhancement if we could configure the Linux agent to report to multiple workspaces.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. IIS logs stopped working :(

    We have been collecting IIS logs from a couple of servers for a month - everything working nicely.

    However 2 days ago no more data was coming into the W3CIISLog table. I tried updating the MMA agent, rebooting the server, verifying IIS settings (hourly rollover). Log files also checks out on local disk of the server. But alas still no new data. We are getting other metrics (perf counters) from MMA, just no more IIS logs.

    Any ideas?

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. OMS files should not be world writable

    The agent creates the following world writable files when it runs.
    /var/opt/microsoft/omsagent/.../state/contentlocationcache.cache
    /var/opt/microsoft/omsagent/.../log/ODSIngestion.status

    Per MS support, these 2 files can safely be changed to 664 permissions without impact to the the agent.
    Having world writable files is a security vulnerability and this should be changed to use the lower permissions.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Display of supported service tags

    The below docment is the network requirements for using the Log Analytics agent. However, there is no description of service tags to use Log Analytics agent.

    https://docs.microsoft.com/en-us/azure/azure-monitor/platform/log-analytics-agent#firewall-requirements

    On the other hand, the service tag is described below, but it is inaccurate and difficult to understand.

    https://docs.microsoft.com/en-us/azure/virtual-network/service-tags-overview#available-service-tags

    Currently, I think we can communicate between Agent and Log Analytics workspace with the following service tags.
    However, especially, "GuestAndHybridManagement" is not listed on the service tag or network requirements docments.
    -AzureMonitor
    -Storage
    -GuestAndHybridManagement

    I would like to check the service tag as official information. Please descrive the service tag for using the Log…

    23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Add Proxy property to Heartbeat data type

    Please add a proxy property to the Heartbeat data type. It doesn't have to be the actual TCP socket, it can be a Y/N. Just something that can be queried to definitively identify if an agent has been configured to use a proxy.

    Network changes within firewalled environments can result in agents being quietly cutoff from Log Analytics. When these events occur it may be weeks before someone notices in non-production environments. Hundreds of agents are affected at a time. Proxies are most often required in DMZ's where tcp/443 access to the internet is blocked.

    The ability to query for…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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.

  7. Request to add BMC Remedy partner type in ITSM Connection

    Hi Team,

    Could you please add BMC Remedy partner type in ITSM connection in LogicApps as this connection is not available which is commonly used tool in most of the software companies.
    Adding this connector will help us to automatically creates remedy tickets whenever there is a failure in ADF or if any component reaches threshold limits

    90 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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. Support for OpenSSL 1.1.*

    Please add support for the latest major version of OpenSSL 1.1. for Linux. Now I am not able to install the agent for Linux because I don't have supported version of OpenSSL (requires 0.9.8, 1.0.*, I have 1.1.0h).

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Update required for Amazon Linux to current version  

    Using OMS with Amazon Linux, last supported version is 2012.09 --> 2015.09 (x86/x64). Newer version of Amazon Linux required for reporting into OMS

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Surface hub cannot connect to OMS using a proxy

    we documented at https://technet.microsoft.com/en-us/itpro/surface-hub/monitor-surface-hub?f=255&MSPPError=-2147217396:

    Note
    Surface Hub does not currently support the use of a proxy server to communicate with the OMS service.

    However, in most customer environment a proxy cannot be bypassed. This limitiation must be changed to allow the SurfaceHub OMS Agent to communicate with the OMS Workspace over a Proxy.

    25 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. OMS agent for macOS

    I'd like to be able to push syslog and other data data from macOS to Log Analytics, however there is not OMS agent for macOS.

    111 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Disable Agent Data Collection from OMS Portal

    Allow to enable/disable/schedule data collection of specific agents. This allows keeping data volume down during tests (e.g. pen or security testing) that might generate lots of events that could you go over the licensed data collection threshold. Maybe combinable with OMS Alert supression.

    31 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Upgrade the version of the ruby bundled with the Linux oms agent

    A lot of FluentD plugins depend on the activesupport gem, which in turn depends on a Ruby version >= 2.2.2. This Ruby version in particular solves a nasty security bug related to SSL.

    The OMS agent bundles a Ruby interpreter version prior to 2.2.2, which prevents us from using a lot of useful fluentd plugins.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Fix Bug in Agent

    We started seeing this error after installing the OMS agent on our servers.

    An unmarshaling policy check was performed when unmarshaling a custom marshaled object and the class {45FB4600-E6E8-4928-B25E-50476FF79425} was rejected.

    A quick search on the internet shows other people have the same error after installing the OMS agent also.

    109 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    We’re aware of an issue that can cause this error to be logged when the Update Assessment solution is installed.
    You can check if this is what you’re seeing my temporarily removing the Update Assessment solution and confirming the errors stop.

    The Update Assessment solution functionality is not affected and you can safely ignore this error.

  15. SCOM-OMS prerequisites checker tool

    Tool which can be used to do prerequisite check for connection between Agent/MS and OMS.
    Based on firewall requirements:
    https://technet.microsoft.com/en-us/library/mt484101.aspx
    including option for Proxy server and Proxy user account.
    It would be a great help for deployment and troubleshooting scenarios.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. MSI-based Windows agent for Intune compatibility

    OMS Windows agent as MSI installer rather than a .exe setup. This enables the agent to be directly deployable wo Windows 10 devices through Intune and OMA-DM.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. The health service HTTP module exceeded number of attempts to post data

    Trying to configure the OMS/SCOM integration.. but the above error comes into the eventlog.. in the PerfMon i see continuous spikes of the system trying to send data..

    not sure if the URL is correct.. but unknown where to configure it:
    The health service HTTP module exceeded number of attempts to post data URL: https://.ods.opinsights.azure.com/ProtectionStatusDataService.svc/PostDataItems. Dropping data batch.

    System


    • Provider

    [ Name] HealthService


    • EventID 2136

    [ Qualifiers] 32768

    Level 2

    Task 0

    Keywords 0x80000000000000

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. vpn

    Add in a monitor to check for Site to Site VPN connectivity between Azure and On-Premise Connection.
    Seeing as we cannot manage fail-over from a customer site, with fail-over internet connections, have a monitor that can check the site to site VPN and push the secondary internet connection to Azure if the main/ primary/ preferred connection fails for a defined period of time. Needs to be defined as each site/ MSP/ ISP is different, default of 5 minutes.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Multihome agents

    It would be fantastic if we could multihome agents to various workspaces.
    Right now we use the SCOM agent to connect to OMS, which means one OMS workspace. But we would like to have multiple workspaces depending on type of server (eg Production servers, Dev servers, application servers etc).

    I understand we can multihome OMS to different workspaces by multihoming the SCOM agent to different SCOM management groups, but having an entire management group set up just so agents can talk to different OMS workspaces is like swatting a fly with a sledgehammer.
    Even if we can manually configure each…

    74 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Push\Install of Microsoft Monitoring Agent from OMS

    If you really want this to be used for stand alone clients, which I think is a great idea for the hybrid cloud, there needs to be an easier way to get the agent installed on those devices.

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base