atlas_rb 1.8.9 → 1.8.10

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1fd50831467b065989eb0ec39af5f96b87622c5d0e161e0e6a5bdef61764505a
-  data.tar.gz: 55c36e14086a0fab3776771c797af98c9a431cca3f0b09f14ffac478ab58067c
+  metadata.gz: 2a1ca62f7d0e0d49e63754618a22967d8a89a4496c05c894bbbff7f13903e94d
+  data.tar.gz: 5645596297711e7cc464645d249b91b4b62108eaf71978f9d07ffed9590043cd
 SHA512:
-  metadata.gz: 7aea8252388df4686a31174ca154b7e76da1d97dd16a8509f773bd2b918dfb282ccb93960f5138b0581df9d32d20c45a0f8cf4a1475dda787468644e1d83cdbd
-  data.tar.gz: 25e3ecf9a7cc353645a8a1ad76700523bba185895fcf1df13b9b098549a45287fb3a9c41abb0eefa559f5e1d8b4c8c4b81b7c16e5e418f4cee39e5f0d554dc56
+  metadata.gz: acd99d449e3dd94bb23cfdeabfc1190d2a074e5bfe07a2a4a8e54723fad47680f525d52e761f5ccee50ac1b464a39b889331e6468fe63bb9a0b06f8d17526262
+  data.tar.gz: c2d0db210a2a66cb41bc68baec3b6158916a86866c9a20182efc1bc2240f26e0c00357e340d08b4313312e239fabc9338bbca3f6face3c9d0576ef13d9f1f74d

data/.version

@@ -1 +1 @@
-1.8.9
+1.8.10

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    atlas_rb (1.8.9)
+    atlas_rb (1.8.10)
       faraday (~> 2.7)
       faraday-follow_redirects (~> 0.3.0)
       faraday-multipart (~> 1)

data/lib/atlas_rb/faraday_helper.rb

@@ -36,9 +36,28 @@ module AtlasRb
   # If neither a signing key nor `ATLAS_JWT` is configured there is no relay
   # credential, so the transport raises {AtlasRb::ConfigurationError}.
   #
+  # ## Instrumentation
+  #
+  # Every builder brackets its request in an `ActiveSupport::Notifications`
+  # event named **`request.atlas_rb`** (Faraday's `:instrumentation`
+  # middleware, wired as the *outermost* handler so a redirect hop — e.g. the
+  # `/resources/:noid` NOID resolver — folds into one event per logical call
+  # rather than being double-counted). The payload is the Faraday `env`, so a
+  # subscriber reads `payload.method` / `payload.url` and the event's duration.
+  # This lets a host count/time Atlas round-trips (an N+1-over-HTTP detector)
+  # without reaching into gem internals. It is guarded on
+  # `defined?(ActiveSupport::Notifications)`: Rails hosts get the events; the
+  # headless BYO-JWT path (no AS loaded) is unaffected. With no subscriber
+  # attached the emit degrades to a listener lookup + `yield`, so it is safe to
+  # leave in the stack permanently — opt-in lives entirely on the consumer side.
+  #
   # The module is mixed in via `extend`, so its methods become class methods on
   # the host (e.g. `AtlasRb::Work.connection({})`).
   module FaradayHelper
+    # ActiveSupport::Notifications event name emitted per outbound Atlas request.
+    # A dedicated name (not Faraday's default `request.faraday`) so a host that
+    # also uses Faraday for other clients can subscribe to Atlas traffic alone.
+    INSTRUMENTATION_EVENT = "request.atlas_rb"
     # Wire contract Atlas enforces for relay-signing assertions (see Atlas
     # ApplicationController#verify_cerberus_assertion). iss/aud are fixed; the
     # short TTL bounds replay (Atlas allows 30s leeway on exp).
@@ -83,6 +102,7 @@ module AtlasRb
         params: params,
         headers: headers
       ) do |f|
+        instrument(f)
         f.use AtlasRb::Middleware::RaiseOnStaleResource
         f.use AtlasRb::Middleware::RaiseOnResourceError
         f.response :follow_redirects
@@ -123,6 +143,7 @@ module AtlasRb
         url: ENV.fetch("ATLAS_URL", nil),
         headers: headers
       ) do |f|
+        instrument(f)
         f.use AtlasRb::Middleware::RaiseOnStaleResource
         # Translate Atlas's verify-on-ingest 422 (fixity_mismatch /
         # unsupported_digest_algorithm) into a typed FixityMismatchError —
@@ -190,6 +211,7 @@ module AtlasRb
         params: params,
         headers: headers
       ) do |f|
+        instrument(f)
         f.response :follow_redirects
         f.adapter Faraday.default_adapter
       end
@@ -197,6 +219,20 @@ module AtlasRb
 
     private
 
+    # Register Faraday's instrumentation middleware as the OUTERMOST handler so
+    # each logical call emits exactly one {INSTRUMENTATION_EVENT} — a redirect
+    # hop (e.g. the `/resources/:noid` resolver) is bracketed with the request
+    # it redirects to, not counted twice. Guarded on
+    # `defined?(ActiveSupport::Notifications)` because Faraday defaults its
+    # instrumenter to that constant and would `NameError` at build time on the
+    # headless path where ActiveSupport isn't loaded; there, the emit is simply
+    # never wired and the transport is unaffected.
+    def instrument(builder)
+      return unless defined?(ActiveSupport::Notifications)
+
+      builder.request :instrumentation, name: INSTRUMENTATION_EVENT
+    end
+
     # Build the auth + identity headers shared by {#connection} and {#multipart}.
     # Precedence: ATLAS_JWT (BYO-JWT) > relay-signing. The acting nuid /
     # on_behalf_of fall through to the configured `default_nuid` /

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: atlas_rb
 version: !ruby/object:Gem::Version
-  version: 1.8.9
+  version: 1.8.10
 platform: ruby
 authors:
 - David Cliff