[TRIVIAL] Fix banned solvers metric

cowprotocol · Feb 27, 2025 · cb4420d · cb4420d
1 parent 7d31849
commit cb4420d
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/crates/autopilot/src/domain/competition/participation_guard/db.rs b/crates/autopilot/src/domain/competition/participation_guard/db.rs
@@ -160,7 +160,8 @@ impl SolverValidator {
             .map(|driver| {
                 Metrics::get()
                     .banned_solver
-                    .with_label_values(&[driver.name.as_ref(), ban_reason.as_str()]);
+                    .with_label_values(&[driver.name.as_ref(), ban_reason.as_str()])
+                    .inc();
                 // Check if solver accepted this feature. This should be removed once the
                 // CIP making this mandatory has been approved.
                 if driver.requested_timeout_on_problems {

diff --git a/crates/autopilot/src/domain/mod.rs b/crates/autopilot/src/domain/mod.rs
@@ -21,7 +21,7 @@ pub struct Metrics {
     /// How many times the solver marked as non-settling based on the database
     /// statistics.
     #[metric(labels("solver", "reason"))]
-    pub banned_solver: prometheus::IntCounterVec,
+    pub banned_solver: prometheus::IntGaugeVec,
 }
 
 impl Metrics {