After configuring Vertica and its related components, you can view the overall configuration status of these components in the Performance Upgrade page in ZCC. For more information, see Viewing the Configuration Status.
However, if you want to continuously monitor the status of each of the components within ZooKeeper, Kafka and Vertica, see Monitoring Diagnostics.
To view the configuration status of the ZooKeeper, Kafka, Vertica clusters and the Bulk Data Migration process, you can navigate to the Getting Started page in ZCC. To navigate to this page, click Configuration > Performance Upgrade.
Each task on this page, includes an icon that indicates the following status:
: the component is successfully configured.
: the component is ready to be configured. For example, the Bulk Data Migration component will be ready to be configured only when Kafka and Vertica components are configured.
: an error has occurred while configuring the component.
To monitor the overall health of the Vertica, ZooKeeper and Kafka clusters, you need to navigate to the Diagnostics page in ZCC. You can also view the status of the Data Sync process on this page. To navigate to the diagnostics page in ZCC, click Diagnostics in the left pane of ZCC.
For more information on debugging issues that are identified by the Diagnostics feature in ZCC, see Debugging and Log Location.
NOTE:If client authentication is not enabled for external CA certificates, then the Data Sync Status and Kafka Cluster status will display correct values only if the Diagnostics page is accessed from a server in which the Kafka role is enabled.
The topics addressed in this section are:
The statuses displayed are as follows:
Up: indicates that all servers are up.
Down: if at least one server is down in the zone, then based on the K factor the relevant status is displayed. For example, the status is displayed as down if at least one server is down and K factor is 0.
Warning: if at least one server is down in the zone, then based on the K factor the relevant status is displayed. For example, the status is displayed as warning if at least one server is down and K factor is 1.
For debugging issues related to the Vertica cluster, see Vertica
The statuses displayed are as follows:
Up: indicates that majority of servers in the cluster are up.
Down: indicates that majority of servers in the cluster are down.
Warning: if one of the servers is down.
NOTE:Besides Vertica, other features in ZENworks require the ZooKeeper services to be up and running at all times. Therefore, even if you do not have Vertica configured in your zone, ZooKeeper should always be active
For debugging issues related to the ZooKeeper cluster, see ZooKeeper
The statuses displayed are as follows:
Up: indicates that all servers are up.
Down: if at least one server is down in the zone, then based on the replication count the relevant status is displayed. For example, the status is displayed as down if at least one server is down in a three node cluster with replication count being 1.
Warning: if at least one server is down in the zone, then based on the replication factor the relevant status is displayed. For example, the status is displayed as warning if at least one server is down in a three node cluster with replication factor being 2.
For the Kafka Cluster, the status of the Kafka Brokers, Kafka Connect and the Schema registry are also displayed.
For debugging issues related to the Kafka cluster, see Debugging and Log Location
The Data Sync Status panel enables you to identify whether the data sync process is running seamlessly or not. This panel displays the status of each Kafka connector that is responsible for syncing data from the RDBMS to Vertica. These connectors help in identifying the rows in the database tables that have been updated and publishes this data to Kafka. The ZENworks loader stream processor services then consumes this data from Kafka and sends it to Vertica.
Along with the connector name and its status, this panel displays the name of the ZENloader stream processors (consumer name) and its status and the names of the server on which the loader services are running. It displays the time at which the ZENloader stream processors last consumed data from Kafka and the time at which this data was last sent to Vertica. It also displays the number of pending records that are yet to be migrated from each Kafka connector to Vertica.
For debugging issues related to the Data Sync process, see Data Migration.