Search the Community

Showing results for tags 'answered'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • From LogicMonitor
    • General Announcements
    • LM Staff Contributions
    • Community Events
  • LogicMonitor Product Discussion
    • Feature Requests
    • LM Exchange
    • Ask the Community

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 4 results

  1. Hi, I love the idea behind the "no data" warning, but it's missing one thing that I think would help make it a little more friendly. We have a few devices that have spotty collection reliability, and it often times leads to use seeing "no data" warnings blowing up in our alerts console for a few minutes and then disappearing. I'd really love to see an option similar to what exists with the actual data points, that is, only show a "no data" if there's "x" consecutive polls of no data. This would prevent the times where we might miss two polls in a row from flooding the alerts.
  2. Idan

    SQL query

    Hi, Looking for the best option to run a SQL query on one of the databases we have on the SQL server, get the result and: 1. Add value to the server properties so I can see it unxer the info. 2. Create graph from the query results Some of the queries may return one value but some several rows like: Pass 100 Failed 200 Ignored 50 I would like to alert e.g. if we have more than 500 failed. I would like to create chart how many pass, failed, ignore. What is the best option to run those queries ? I would like to get automatically the DB name from the SQL and run it on each database that the database name contain "public"
  3. Hi, Like to understand how we can setup the datasource to monitor CMC drive status in LM. currently its enabled SNMP monitoring and it does not help. Need to understand more on this.
  4. From the v75 release notes. "Information, FailureAudit and SuccessAudit have been removed as options for the Windows Eventsource Level filter. Level filters set to these values always had to be used in conjunction with an event ID, making them superfluous." This is a bad change. It wasn't superfluous, it was clear interface design. Here's the unintended consequences to this change: 1) I can't have a single windows event datasource that shows both warnings and errors unless I create a new datasource and not change the filter from the default. 2) Why have a “more urgent than” setting when it doesn’t do anything? See the table below 3) There is no way to set an existing datasource back to the default (more urgent than information) once it has been modified. Here are the options that are possible after the change in the interface. Datasource filter setting What is alerted Notes LEVEL More urgent than Warning Will only alert on Errors Pointless because it’s the same as below LEVEL More urgent than Error Will never alert on anything Pointless because it never alerts LEVEL Equal Error Will only alert on Errors