apidepth 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fe52fa09e05f825f4300ebb638df967a43087c59bbd833eead51101ad784e092
-  data.tar.gz: 90b843525ebc7ee2e8124833593f6f13284baff8e20ba031a9df64abd6dd6867
+  metadata.gz: 3226f968bffa6535e9444dbbec3cd494d0e457138fd288d54f9f48df1e6d6166
+  data.tar.gz: cffca712b07f6501d020ecc54cac0f811dfea18c89c959a778ed048dd4f12d4c
 SHA512:
-  metadata.gz: a570c48989e019f50c32e5c8d56de9b88eac99035bea44fdf2fa9abfd7021a1e4d86141d2837fdbacbf91435110572394cf0efd10139af83faee51f6eaf301bc
-  data.tar.gz: afa912c7e24d9823d1eee500ba521981577df34e7a7dd3200b0d336d0e16a7674d8a26db5624ab2c8dd537c5ce45f92b8a1798a9fbb3e9b9e30013e01b9062ce
+  metadata.gz: 53b8a62f5c91b8998dd13d06c41c64d5922a228f6022534320766fe080b7b9f9c45cb96d93de16cfb542a9709bb10c771e72514671195bde8349562b86dcba58
+  data.tar.gz: 558c43465398f9963d6254ca90167b63b0d7db5ce00735cdb42e900eb37cfa2df4a3b543a2b58ad816191dbad07929c4cb451ea7589e8fe980d6c3040cb16ade

data/README.md

@@ -1,16 +1,22 @@
 # apidepth
 
-Passive outbound API latency monitoring for Rails. Captures real production latency to third-party APIs — Stripe, OpenAI, Twilio, and others — without synthetic probes, without payload capture, and without changes to your application code beyond a one-time initializer.
+Most API monitoring tools measure latency from their servers to the vendor. That's not what your users feel. Apidepth instruments `Net::HTTP` directly — every outbound call your app makes to Stripe, OpenAI, or Twilio is timed at the socket level, from your server. Then it benchmarks your numbers against anonymized fleet data, so when Stripe is slow you can tell if it's you or everyone.
+
+No payload capture. No credentials touch our infrastructure. No changes to your application code beyond a one-time initializer.
 
 ---
 
 ## How it works
 
-Most API monitoring tools run scheduled probes from their own servers and measure latency to a vendor endpoint. That tells you how fast the vendor responds to *them*, from *their* location, to a test request. It doesn't tell you what your users are experiencing.
+**Real traffic, not synthetic probes.** Every outbound HTTP call your application makes to a known vendor is timed at the socket level, tagged with outcome and environment metadata, and batched to the Apidepth collector in the background. The latency number in your dashboard is the number your users feel — not a probe running from a data center somewhere else.
+
+**Fleet benchmarking.** Because Apidepth aggregates anonymized timing data across all customers, your dashboard shows not just "your Stripe p95 is 420ms" but "the fleet median is 280ms — you may have a regional routing issue." That comparison is only possible with real traffic from real deployments, which is why no synthetic probe tool can offer it.
+
+**Proof of Innocence.** When all endpoints to a vendor spike simultaneously, Apidepth surfaces a verdict: *isolated* (the spike is yours alone — likely your code or infrastructure) or *tracking* (the fleet sees the same thing — vendor-side). The attribution card makes it fast to tell ops "it's Stripe, not us."
 
-Apidepth instruments `Net::HTTP` directly. Every outbound HTTP call your application makes to a known vendor is timed at the socket level, tagged with outcome and environment metadata, and batched to the Apidepth collector in the background. No payloads are captured. No credentials touch our infrastructure. The latency measurement is from your server to the vendor — the number your users feel.
+**Alerts and weekly digest.** Apidepth fires alerts when vendor latency crosses your configured threshold and sends a weekly digest summarizing what changed. Monitoring without alerting is passive; this is working for you.
 
-The second differentiator is benchmarking. Because Apidepth aggregates anonymized timing data across all customers, your dashboard can show not just "your Stripe p95 is 420ms" but "the fleet median is 280ms — you may have a regional routing issue." That comparison is only possible with real traffic from real deployments, which is why no synthetic probe tool can offer it.
+**Rate limit intelligence.** Apidepth tracks 429 patterns and projects quota burn-down before you hit the ceiling — with a burn-down card showing time-to-throttle at current request rate.
 
 ---
 

data/lib/apidepth/collector.rb

@@ -234,9 +234,16 @@ module Apidepth
       return if events.empty?
 
       key = Apidepth.configuration.api_key
-      # Nil or empty key: Railtie already warned at boot — skip silently rather
-      # than sending a broken "Bearer " header and burning a failure increment.
-      return if key.nil? || key.empty?
+      if key.nil? || key.empty?
+        unless @warned_no_key
+          @warned_no_key = true
+          Apidepth.logger&.warn(
+            "[Apidepth] No API key configured — events are being dropped. " \
+            "Visit www.apidepth.io to create an account and get your key."
+          )
+        end
+        return
+      end
 
       validate_api_key!(key)
 

data/lib/apidepth/railtie.rb

@@ -8,8 +8,9 @@ module Apidepth
     initializer "apidepth.validate_config", after: :load_config_initializers do
       if Apidepth.configuration.api_key.nil?
         Rails.logger.warn(
-          "[Apidepth] No api_key configured — events will not be delivered. " \
-          "Add `config.api_key = ENV['APIDEPTH_API_KEY']` to config/initializers/apidepth.rb"
+          "[Apidepth] No API key configured — events will not be delivered. " \
+          "Visit www.apidepth.io to create an account and get your key, " \
+          "then add `config.api_key = ENV['APIDEPTH_API_KEY']` to config/initializers/apidepth.rb"
         )
       end
     end

data/lib/apidepth/version.rb

@@ -1,5 +1,5 @@
 # lib/apidepth/version.rb
 
 module Apidepth
-  VERSION = "0.2.0".freeze
+  VERSION = "0.2.1".freeze
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: apidepth
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Apidepth
@@ -138,7 +138,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.10
+rubygems_version: 4.0.11
 specification_version: 4
 summary: Passive outbound API latency monitoring for Rails applications
 test_files: []