Consul provides a built-in CLI and API that allows you to query the most recent information about your cluster, giving you a high-level read into Consul's health and performance. The `consul debug` command monitors your Consul cluster for a configurable period of time (two minutes by default) and writes the results to a `tar.gz` file, providing detailed information that is useful for investigating issues. Consul uses the `go-metrics` library to expose metrics, allowing you to configure a metrics sink to retain your Consul metrics beyond the default one-minute window. This enables comprehensive visibility into all of the metrics introduced in Part 1, and allows you to track your metrics over time, compare them to metrics and logs from other parts of your infrastructure, and get more visibility into your Consul cluster. Additionally, Consul provides a browser-based graphical user interface that provides a high-level overview of services and nodes running in your cluster, allowing you to view summaries of health checks and edit cluster metadata and configuration details within the key-value store. The UI also has some benefit for monitoring, giving you a synopsis of your cluster's status, including the results of health checks on Consul nodes and services ("Passing," "Warning," or "Critical"), and allowing you to discover issues quickly.