Forum Discussion

ldoodle's avatar
ldoodle
Icon for Advisor rankAdvisor
2 months ago

SQL Monitoring Troubles

Hey,

I've just added 4 SQL Servers to our environment. 2 of them worked perfectly and are retrieving all the SQL data.

However, 2 of them aren't learning that SQL is installed: one of them reports WMI access error but wbemtest from the LM collector with the LM collector account details succeeds on both. The other just doesn't seem to know SQL is installed, no errors are shown.

The one with WMI error obviously isn't even retrieving Windows data like CPU and memory. The one with no WMI error is showing this data okay.

I'm not sure where to check for problems in LM - any logs I can look at?

Thanks

4 Replies

Sort By
  • Joe_Williams's avatar
    Joe_Williams
    Icon for Professor rankProfessor
    2 months ago

    Are the various servers on different domains? Or not on a domain at all? Cross realm authentication can be an issue at times with LogicMonitor and how/where creds are set.

  • ldoodle's avatar
    ldoodle
    Icon for Advisor rankAdvisor
    2 months ago

    ...and putting the jdbc.mssql properties in for user and pass has fixed that one with the missing SQL problem.

    Does anyone know why this might be - it's not a common problem across any of our other SQLs (we have more than these 4 new ones today).

    So one today required the wmi properties and one required jdbc.mssql properties. Weird.

  • ldoodle's avatar
    ldoodle
    Icon for Advisor rankAdvisor
    2 months ago

    Strange, putting the LM collector creds as properties has fixed that one with wmi error.

    But the one not retrieving SQL data sources at all is weird.

  • ldoodle's avatar
    ldoodle
    Icon for Advisor rankAdvisor
    2 months ago

    The one with the WMI error is the classic one:

    But as I say, wbemtest works ok with the same creds.