Azure Monitor-Log Analytics

Welcome to the "Azure 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

How can we improve Azure Log Analytics ?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Target Solution packs to group of computers/data centers

    I don't want to use *ALL* solution packs on *ALL* onboarded servers. At the moment the only workaround is to create workspaces by solution pack and maintain your server list by solution packs.

    1) While Adding a Solution; optionally specify groups to target. (e.g. All; only this group members or All groups except members of this group)
    2) Track data/$$ by solution pack and by servers/user defined groups. This can be used to Alert when a SP or computer/group consumes more than expected-->trigger runbook to unload SP on the server.
    3) Configure data flow by restricting (Servers; solutions;group of servers;…

    33 votes
    Sign in
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?

Feedback and Knowledge Base