ezlog 0.9.6 → 0.10.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 178b2810c13ba87a8a1e389a6679e14f06e4b4f05bcc0a84dea797110cfde3a7
-  data.tar.gz: ae3e3abfbf692e3189a5d6e1bfb1efe4ec3ce064e1e61285a2c13b27922e13fe
+  metadata.gz: 522f8d12a7a34a7aa83c51c6729dd212909979a3c0db32ad622436056be3ea03
+  data.tar.gz: ebf173e4431cb016de8e6a14b418b71106221982d3ebc082d53b2ed0a31fd3b5
 SHA512:
-  metadata.gz: 21d6c1fa52dd9b46bbc33fc776d139d3c7c38492cb8f7f47bcfc577c47c53a8014197712993ece0a53807646fff222acca23e803df8af74c32ee820b4b895f7c
-  data.tar.gz: 2ba5df5dcb18e3553f97f4727556626ad386e2e2c4dc16aefe261d3502cbe33d9fc163c439da8aa3a8392359eba43f15ea5a5da7501892da7e6c7e9e149b0553
+  metadata.gz: c9efef1e23b6b8b77689d513665676aad77340d04131ca6241b565ac2cf7e8e78f21dbb0adf8ea06ce2a76008b12d7d350cbd7ea35de6d2228367b486bbda7b8
+  data.tar.gz: 14a749943851eadf758f2e71f0a9680f9af86c2b2895e5a946918d50696fe1f19ccacb090b37f40935d972150fb18af1d6602bb93b711917a471b8d8b4ced249

data/CHANGELOG.md

@@ -1,3 +1,10 @@
+### 0.10.0 (2021-07-01)
+
+[Full Changelog](https://github.com/emartech/ezlog/compare/v0.9.6...v0.10.0)
+
+* Features & enhancements
+  * Do not log exceptions which are handled by Rails. Therefore you can't get false alarms from your exception notifier
+
 ### 0.9.6 (2021-06-30)
 
 [Full Changelog](https://github.com/emartech/ezlog/compare/v0.9.5...v0.9.6)

data/README.md

@@ -93,6 +93,7 @@ In addition to this, Ezlog also does the following:
 * It disables Rails's default logging of uncaught errors and injects its own error logger into the application, which
   * logs 1 line per error, including the error's name and context (stack trace, etc.),
   * logs every error at ERROR level instead of the default FATAL.
+  * does not log exceptions which are handled by Rails (`ActionDispatch::ExceptionWrapper.rescue_responses`)
 * It disables Rails's default request logging, which logs several lines per event during the processing of an action,
   and replaces the default Rack access log with its own access log middleware. The end result is an access log that
   * contains all relevant information (request ID, method, path, params, client IP, duration and response status code), and

data/lib/ezlog/rails/log_exceptions.rb

@@ -9,9 +9,15 @@ module Ezlog
       def call(env)
         @app.call(env)
       rescue Exception => exception
-        @logger.error exception
+        @logger.error exception unless handled?(exception)
         raise
       end
+
+      private
+
+      def handled?(exception)
+        ActionDispatch::ExceptionWrapper.rescue_responses.key? exception.class.name
+      end
     end
   end
 end

data/lib/ezlog/rspec/matchers.rb

@@ -55,3 +55,5 @@ RSpec::Matchers.define :log do
     log_output_is_expected.to include_log_message(expected).at_level(log_level)
   end
 end
+
+RSpec::Matchers.define_negated_matcher :not_log, :log

data/lib/ezlog/version.rb

@@ -1,3 +1,3 @@
 module Ezlog
-  VERSION = '0.9.6'
+  VERSION = '0.10.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ezlog
 version: !ruby/object:Gem::Version
-  version: 0.9.6
+  version: 0.10.0
 platform: ruby
 authors:
 - Zoltan Ormandi
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2021-06-30 00:00:00.000000000 Z
+date: 2021-07-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: logging
@@ -192,7 +192,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.6
+rubygems_version: 3.1.2
 signing_key: 
 specification_version: 4
 summary: A zero-configuration logging solution for projects using Sidekiq, Rails,