Exploring the Prometheus Web Interface
The Runtime and Build Information
By going to Status > Runtime & Build Information, you can see the build and run environment of your instance. Here is some of the information available:
Configuration reload: Whether the last configuration reload was applied successfully.
WAL corruptions: The number of WAL corruptions. This could indicate a problem with the write-ahead log.
ℹ️ A reminder: The WAL is the write-ahead log that stores incoming samples before they are written to the main storage.
Goroutines: Prometheus is developed in Go and uses a mechanism called goroutines. This metric shows the number of goroutines that are currently running.
ℹ️ Goroutines are lightweight threads managed by the Go runtime, allowing tasks to be executed concurrently with low resource consumption.
GOMAXPROCS: This is the maximum number of CPUs that can be executing simultaneously. This is set to the number of CPUs available on the machine.
Storage retention: The retention period for the data in storage. By default, data is deleted after 15 days.
And more...
Here is a summary of what you can find on this page:
| Information | Description |
|---|---|
| Start time | The time when the Prometheus server was started. |
| Working directory | The directory that is used as the working directory for the Prometheus server. |
| Configuration reload | The status of the last configuration reload attempt. |
| Last successful configuration reload | The timestamp of the last successful configuration reload. |
| WAL corruptions | The number of corruptions detected in the Write-Ahead Log (WAL). |
| Goroutines | The number of goroutines currently running in the Prometheus server. |
| GOMAXPROCS |
Observability with Prometheus and Grafana
A Complete Hands-On Guide to Operational Clarity in Cloud-Native SystemsEnroll now to unlock all content and receive all future updates for free.