Details not showing up properly for clustered instances about opserver HOT 6 CLOSED

Are you using failover cluster instances? The dashboard is currently for Availability Group clusters, since that's what I have to test on here at Stack Exchange. I do mean to get failover cluster support in, but I'll need to setup a local lab to test that here first.

from opserver.

HI Nick, yes I am using Failover Clustered Instances, not AG's. FCI support would be greatly appreciated. Thanks.

from opserver.

@NickCraver I am seeing exactly the same issue for standalone named instances. Any chance these issue is due to the fact that my failover clustered instances are named not because they are not in Availablity Groups?

from opserver.

It's due to the objectname property which is usually SQLServer but in the case of a named instance is MSSQL$InstanceName

https://github.com/opserver/Opserver/blob/master/Opserver.Core/Data/SQL/SQLInstance.cs#L44

I'd send a pull request, but I'm a terrible person.

from opserver.

@DaniSQL In the config you have a name and connectionString, can you set the objectName property to the Instance? like @jamessantiago says above? Something like this:

{
  "name": "MyServer",
  "connectionString": "Data Source=MyServer\\MyInstance;Initial Catalog=bob;Integrated Security=SSPI;",
  "objectName": "MSSQL$MyInstance"
},

If that works fine, I'll adjust the default detection so that works for most people out f the box.

from opserver.

@NickCraver, @jamessantiago - awesome! That fixed it and I am now able to see Performance, Size and Cache details both for clustered and standalone named instances. However the clustered instances still show the state as "offline" and no CPU information.

from opserver.