ref(instr): Instrument rate limit timings for new processing pipeline (#5389)

Author: Dav1dde

relay-server/src/processing/limits.rs

@@ -9,6 +9,7 @@ use crate::processing::{Context, Counted, Managed, Rejected};
 use crate::services::{
     global_rate_limits::GlobalRateLimitsServiceHandle, projects::cache::ProjectCacheHandle,
 };
+use crate::statsd::RelayTimers;
 
 #[cfg(feature = "processing")]
 type Redis = relay_quotas::RedisRateLimiter<GlobalRateLimitsServiceHandle>;
@@ -71,7 +72,21 @@ impl QuotaRateLimiter {
             redis::CombinedRateLimiter(limiter, redis)
         };
 
-        data.enforce(limiter, ctx).await
+        let ty = match self.has_redis() {
+            true => "consistent",
+            false => "cached",
+        };
+        relay_statsd::metric!(timer(RelayTimers::EventProcessingRateLimiting), type = ty, unit = std::any::type_name::<T>(), {
+            data.enforce(limiter, ctx).await
+        })
+    }
+
+    fn has_redis(&self) -> bool {
+        #[cfg(feature = "processing")]
+        if self.redis.is_some() {
+            return true;
+        }
+        false
     }
 }
 

relay-server/src/statsd.rs

@@ -389,6 +389,8 @@ pub enum RelayTimers {
     ///
     /// This metric is tagged with:
     ///  - `type`: The type of limiter executed, `cached` or `consistent`.
+    ///  - `unit`: The item/unit of work which is being rate limited, only available for new
+    ///    processing pipelines.
     EventProcessingRateLimiting,
     /// Time in milliseconds spent in data scrubbing for the current event. Data scrubbing happens
     /// last before serializing the event back to JSON.