ez_logs_agent 0.1.7 → 0.1.9

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e1155fac143bb0af7e99c95a8dde26764f1c3f2bfab758beec239adef8bfab06
-  data.tar.gz: d87b5b4cc03d73117e0b1759b26c149a73e8bd2c1aa670a8b79f5c0b4a0fe7de
+  metadata.gz: 45c8553757f1910ef31222e012e48b699b7ab5c4345d631c3bbcce370fc27363
+  data.tar.gz: 2f966ab6c6886970603e637b11015c1201b032b44c2f7d9996513a88de7d01eb
 SHA512:
-  metadata.gz: 2b91f112497b1443ffe044215819e0fb9a26748026bd43859ed2b239eacb53920cb6ae27c455f34693b46e56cc62ff1775a6177b1e76805f603f2402737a5cf3
-  data.tar.gz: dd0ae94996e329e795da19f2017a165cbf3e81e81aa8ee493e1a1d086abc02dd1f01bd61ac12fc5c8d08192863877bd83420903e113ada489788465e7f4fcac8
+  metadata.gz: '08d182e4ac18aee7b2104b7c52c0b6e240de2b613c0815851663a5933f2bb62f2f7ce9a43c1d6be370078820121b5498ad3d95ff2e68da8f8faee2f6bc062449'
+  data.tar.gz: fb8b9a2cbc66f62bb8e0a054cc11e1fb0b25d741d910f25136e12700571197ac8371669a080259d2631b32d61e3dbbdfbc359134e173c6d95ce70fa3fc753af7

data/CHANGELOG.md

@@ -2,6 +2,40 @@
 
 All notable changes to this project will be documented in this file.
 
+## [0.1.9] — 2026-06-05
+
+### Fixed
+- `Sanitizer` no longer collapses ActiveJob record references
+  (`{"_aj_globalid" => "gid://app/Model/id"}`) to `"[Object]"` at the
+  depth-3 cap. These one-key wrapper hashes pass through verbatim so
+  the server can display *which* record a job ran on
+  (e.g. ActionMailer's `Record 1` field now reads `User #42` instead
+  of `[Object]`).
+
+The carve-out is narrow: only the exact `{"_aj_globalid" => "gid://..."}`
+shape is exempt. Multi-key hashes, non-GID values, and any other
+nested structure still hit the existing graph-protection rules
+(depth cap, array truncation, non-primitive collapse) unchanged. No
+wire-format change.
+
+## [0.1.8] — 2026-05-29
+
+### Changed
+- Install template (`rails generate ez_logs_agent:install`) now
+  pre-fills `config.server_url` with the real SaaS endpoint
+  (`https://app.ezlogs.io`) and `config.project_token` with
+  `ENV["EZLOGS_API_KEY"]`, uncommented. Self-hosters override via
+  `ENV["EZLOGS_SERVER_URL"]`. New customers only need to set one
+  env var (the API key); they no longer have to know to uncomment
+  the URL line or guess the right value.
+- Documentation (`QUICKSTART.md`, `CONFIGURATION.md`, `FAQ.md`) uses
+  the real product URLs (`app.ezlogs.io`, `ezlogs.io/pricing`)
+  instead of `your-ezlogs-server.com` placeholders.
+
+No wire-format or runtime-behavior changes. Existing customers'
+already-generated initializer files are untouched — the generator
+doesn't rewrite them. Only fresh installs see the new defaults.
+
 ## [0.1.7] — 2026-05-28
 
 ### Changed

data/lib/ez_logs_agent/sanitizer.rb

@@ -96,6 +96,12 @@ module EzLogsAgent
       private
 
       def sanitize_nested_object(hash, depth)
+        # ActiveJob serializes record refs as `{"_aj_globalid" => "gid://..."}`.
+        # Preserve these even past the depth limit so a record reference
+        # survives the [Object] collapse and the server can display WHICH
+        # record the job ran on. Display formatting (gid → "User #42") is
+        # the server's job; the agent's job is to keep the data on the wire.
+        return hash if global_id_hash?(hash)
         return "[Object]" if depth >= MAX_NESTING_DEPTH
         return {} if hash.empty?
 
@@ -145,6 +151,16 @@ module EzLogsAgent
           value.is_a?(TrueClass) ||
           value.is_a?(FalseClass)
       end
+
+      # True iff `hash` is the exact one-key shape ActiveJob uses to serialize
+      # an ActiveRecord (or any GlobalID::Identification) argument:
+      # `{"_aj_globalid" => "gid://..."}`. Used to exempt these hashes from
+      # the depth-limit collapse so the wire still carries the record ref.
+      def global_id_hash?(hash)
+        return false unless hash.is_a?(Hash) && hash.size == 1
+        gid = hash["_aj_globalid"] || hash[:_aj_globalid]
+        gid.is_a?(String) && gid.start_with?("gid://")
+      end
     end
   end
 end

data/lib/ez_logs_agent/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module EzLogsAgent
-  VERSION = "0.1.7"
+  VERSION = "0.1.9"
 end

data/lib/generators/ez_logs_agent/install/templates/ez_logs_agent.rb.tt

@@ -10,14 +10,13 @@ EzLogsAgent.configure do |config|
   # REQUIRED SETTINGS
   # =============================================================================
 
-  # URL of the EzLogs server (required)
-  # Default: nil (must be set for events to be sent)
-  # config.server_url = "https://your-ezlogs-server.com"
-
-  # API key for authentication (required)
-  # Get this from your EzLogs dashboard: Settings → API Keys
-  # Default: nil
-  # config.project_token = "your-api-key-here"
+  # URL of the EzLogs server. Defaults to the EzLogs SaaS endpoint, which is
+  # the same URL for every customer — tenants are identified by API key, not
+  # by URL. Override only if you self-host.
+  config.server_url = ENV.fetch("EZLOGS_SERVER_URL", "https://app.ezlogs.io")
+
+  # API key for your tenant. Get one at https://app.ezlogs.io/settings/api-keys.
+  config.project_token = ENV["EZLOGS_API_KEY"]
 
   # =============================================================================
   # CAPTURE SETTINGS

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: ez_logs_agent
 version: !ruby/object:Gem::Version
-  version: 0.1.7
+  version: 0.1.9
 platform: ruby
 authors:
 - dezsirazvan
 bindir: bin
 cert_chain: []
-date: 2026-05-28 00:00:00.000000000 Z
+date: 2026-06-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: request_store