You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think using named instances is expected, but using listeners also works, except for showing details by nodes in sql/servers in GetAvailabilityGroups.
@NickCraver, what do you think about using listeners with some limitation? I mean the availability of data only from primary replicas.
I have WSFC clusters with multiple AG as resources. The following snippet is an example of my Opserver configuration:
But with the configuration described, I get the following result:
If go deeper into the source code, we will find the following code:
Something like that:
{{machine}} == {{machine}}+{{instance}}
. All elements will have theIsLocal
property, evaluated tofalse
.The
MemberName
property of theAGClusterMemberInfo
class is mapped to themember_name
column:Then the following method is called:
If the
IsLocal
property is false, the default object will be returned - State and Votes columns will are empty on SQL dashboard.If I change the code above to:
Everything works fine, anyway for my configuration.
But I'm not sure about this approach. Maybe I misconfigured Opserver? Or is there really an mistake?
The text was updated successfully, but these errors were encountered: