<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h4 class="title">
      <a name="group-replication-observability">
      </a>
      20.1.4.4 Observability
     </h4>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045134321264">
  </a>
  <p>
   There is a lot of automation built into the Group Replication
        plugin. Nonetheless, you might sometimes need to understand what
        is happening behind the scenes. This is where the
        instrumentation of Group Replication and Performance Schema
        becomes important. The entire state of the system (including the
        view, conflict statistics and service states) can be queried
        through Performance Schema tables. The distributed nature of the
        replication protocol and the fact that server instances agree
        and thus synchronize on transactions and metadata makes it
        simpler to inspect the state of the group. For example, you can
        connect to a single server in the group and obtain both local
        and global information by issuing select statements on the Group
        Replication related Performance Schema tables. For more
        information, see
   <a class="xref" href="group-replication-monitoring.html" title="20.4 Monitoring Group Replication">
    Section 20.4, “Monitoring Group Replication”
   </a>
   .
  </p>
 </div>
 <br/>
</div>
