Resets the value of the gauge identified by spec. Raises Prometheus.UnknownMetricError exception if a gauge for spec can't be found.<br> Raises Prometheus.InvalidMetricArityError exception if labels count mismatch. Sets the gauge identified by spec to value.

April 24, 2026 - A Gauge tracks a value that can go up and down. Use it for things you sample at a point in time — active connections, queue depth, memory usage, temperature. from prometheus_client import Gauge g = Gauge('my_inprogress_requests', 'Description of gauge') g.inc() # Increment by 1 g.dec(10) ...

January 30, 2026 - Track resource usage as a percentage or absolute value. from prometheus_client import Gauge import psutil cpu_usage = Gauge( 'system_cpu_usage_percent', 'Current CPU usage percentage', ['cpu'] ) memory_usage_percent = Gauge( 'system_memory_usage_percent', 'Current memory usage percentage' ) disk_usage = Gauge( 'system_disk_usage_bytes', 'Current disk usage in bytes', ['mount_point'] ) def collect_system_metrics(): # CPU per core for i, percent in enumerate(psutil.cpu_percent(percpu=True)): cpu_usage.labels(cpu=f'cpu{i}').set(percent) # Memory mem = psutil.virtual_memory() memory_usage_percent.set(mem.percent) # Disk per mount point for partition in psutil.disk_partitions(): usage = psutil.disk_usage(partition.mountpoint) disk_usage.labels(mount_point=partition.mountpoint).set(usage.used)

February 21, 2026 - Use .Set() when your application can retrieve the current value directly, such as from in-memory queues or counters. With prometheus_client, define the gauge and call .set() directly.

November 6, 2020 - // // A Gauge is typically used ... use NewGauge. type Gauge interface { Metric · Collector · · // Set sets the Gauge to an arbitrary value....

v_labels ~label_names ~help ~namespace ~subsystem name is a family of metrics with full name namespace_subsystem_name and documentation string help. Each metric in the family will provide a value for each of the labels.

// // A Gauge is typically used ... use NewGauge. type Gauge interface { Metric · Collector · · // Set sets the Gauge to an arbitrary value....

A gauge metric to represent a value that can arbitrarily go up and down. The class represents the metric type gauge: https://prometheus.io/docs/concepts/metric_types/#gauge

January 1, 2023 - Prometheus::addGauge('User count') ->label('status') ->value(function() { return [ [User::where('status', 'active')->count(), ['active']], [User::where('status', 'inactive')->count(), ['inactive']], ]; }); Instead of using multiple methods, ...

Hello, the best solution is probably to use a Custom Collector to gather the temperature information and only create a gauge if there is a value. This keeps the behavior of reading the thermometer when Prometheus scrapes the endpoint, and allows you lots of control over the results.

Gauges are typically used for measured values like temperatures or current memory usage, but also "counts" that can go up and down, like the number of concurrent requests.

November 6, 2023 - Use Flux to query and transform Prometheus gauge metrics stored in InfluxDB. A gauge is a metric that represents a single numerical value that can arbitrarily go up and down.

September 15, 2016 - (r@turbot)4> prometheus_gauge:new([{name,"name"},{help,"help me!"}]). ok (r@turbot)5> prometheus_gauge:value("name"). undefined (r@turbot)6> prometheus_gauge:reset("name"). false (r@turbot)7> prometheus_gauge:value("name"). undefined (r@turbot)8> prometheus_gauge:set("name",1).

I'm considering to use a gauge to reflect the evolution of a boolean value. Knowing that the set method of a Gauge cast the given value as a float, I could call directly my_gauge.set(my_bool_value), and have it set to 0.0 or 1.0.

April 11, 2023 - It have an gauge metric for conn pool stats, defined as: ... On other hand, another library we used only expose an Store method to the user, which is been called when the library want to set a metric to an concrete value (with different labels group), we implement Store use gauge.Set method.

July 21, 2025 - The rule of thumb is to always use set()Copy if you can query the current value from a source of truth (like a database or a system file). You only use inc()Copy and dec()Copy when no such source exists, and you can only observe events as they happen. When plotting gauge metrics, accessing its raw value is the most direct way to visualize its behavior over time:

December 26, 2016 - Gauges can go up and down over time, and scrapes take a snapshot of the current value. There's no potential for messing around with moving averages or resets, as there is with counters. Where Prometheus differs from other other monitoring systems is the API for gauges in instrumentation. The Prometheus Gauge API covers all the gauge uses cases in one place. It has inc, dec, and set methods, plus various utility functions for common uses such as setting the current time.

February 5, 2021 - The max_over_time function calculates the gauge's maximum value over the time range. ... Most Prometheus functions do work with gauges, but there are some important exceptions such as increase and rate.