Search the Community

Showing results for tags 'troubleshooter'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • From LogicMonitor
    • Product 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 2 results

  1. Hello, I have recently seen a few of these tickets com across the board and was wondering if anyone would be able to give me a quick breakdown as to what this actually is and what the benefits would be to add this into the instance. SQL Server Troubleshooter-MSSQLSERVER Missing JDBC connection string. Manually add one to mssql.mssqlserver.mssql_url or check login informations exitCode A Microsoft SQL server has configuration problems or a logon error. MSSQLSERVER Missing JDBC connection string. Manually add one to mssql.mssqlserver.mssql_url or check login informations Th
  2. A hack of the Microsoft_SQLServer_SystemJobs datasource that will alert you in the event that the available credentials cannot gather SQL System Jobs. In brief, it attempts the same SQL query that the original DataSource runs, but creates no instances on a success - in the event of a failure, it will generate one instance whose description will be the error message, and one datapoint will be applied that will trigger a warning alert after a couple of minutes. It'll look a bit like this where the SQL query fails: Note this *only* tries the query for System Jobs ('select * f