Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | private method is not needed | Aaron Patterson | 2010-07-17 | 1 | -12/+2 | |
| | ||||||
* | removing Binding class | Aaron Patterson | 2010-07-17 | 1 | -14/+4 | |
| | ||||||
* | use === to avoid regular expression creation, and speed up string comparison | Aaron Patterson | 2010-07-17 | 1 | -9/+3 | |
| | ||||||
* | Event should be aware if yielded block failed or not. | José Valim | 2010-05-02 | 1 | -3/+5 | |
| | ||||||
* | Make notifications go off even when an error is raised, so that we capture ↵ | Justin George | 2010-05-02 | 1 | -3/+7 | |
| | | | | | | | | | | | | | | the underlying performance data [#4505 state:resolved] This is important when trying to keep track of many layers of interrelated calls i.e.: ActiveRecord::Base.transaction do MyModel.find(1) #ActiveRecord::NotFound end # should capture the full time until the error propagation Signed-off-by: José Valim <jose.valim@gmail.com> | |||||
* | allow unsubscribe by name or subscription [#4433 state:resolved] | David Chelimsky | 2010-04-24 | 1 | -5/+15 | |
| | | | | Signed-off-by: Jeremy Kemper <jeremy@bitsweat.net> | |||||
* | Mark bang instrumentations as something that you shuold not be listening to. | José Valim | 2010-03-17 | 1 | -1/+1 | |
| | ||||||
* | Optimize AS::Notifications to remember which subscribers don't match and not ↵ | Carlhuda | 2010-03-01 | 1 | -3/+12 | |
| | | | | run them. This will allow notifications that are only useful in dev or testing to run efficiently in production. | |||||
* | You can unsubscribe a subscriber | Carlhuda | 2010-03-01 | 1 | -3/+8 | |
| | ||||||
* | AS::Subscriber is not a LogSubscriber | Carlhuda | 2010-03-01 | 1 | -2/+2 | |
| | ||||||
* | Rename Rails::Subscriber to Rails::LogSubscriber | Prem Sichanugrist | 2010-02-16 | 1 | -5/+5 | |
| | ||||||
* | Remove instrument! and require thread from AS::Notifications. | José Valim | 2010-02-04 | 2 | -12/+1 | |
| | ||||||
* | Default to sync instrumentation. | José Valim | 2010-01-21 | 1 | -33/+3 | |
| | ||||||
* | Add ActionDispatch::Notifications middleware. | José Valim | 2010-01-17 | 1 | -0/+9 | |
| | ||||||
* | Yield the payload notifications for further modification (like adding the ↵ | José Valim | 2010-01-15 | 1 | -8/+2 | |
| | | | | result). | |||||
* | Add instrument! to notifications which adds the result to the payload. | José Valim | 2010-01-14 | 1 | -1/+9 | |
| | ||||||
* | Do not send notifications when instrumentation raise an error. | José Valim | 2010-01-13 | 1 | -2/+2 | |
| | ||||||
* | Expose Instrumenter id in Notifications. | José Valim | 2010-01-04 | 1 | -0/+2 | |
| | ||||||
* | Remove ActionView inline logging to ActiveSupport::Notifications and create ↵ | José Valim | 2009-12-26 | 1 | -6/+5 | |
| | | | | ActionController::Base#log_event, so everything can be logged within one listener. Also expose log_process_action as a hook for different modules to include their own information during the action processing. This allow ActiveRecord to hook and any other ORM. Finally, this commit changes 'Processing' and 'Rendering' in logs to 'Processed' and 'Rendered' because at the point it's logged, everying already happened. | |||||
* | Notifications: synchronous fanout queue pushes events to subscribers rather ↵ | Jeremy Kemper | 2009-11-29 | 1 | -22/+39 | |
| | | | | than having them concurrently pull | |||||
* | Notifications: extract central Notifier, cordon off the internal Fanout ↵ | Jeremy Kemper | 2009-11-28 | 2 | -0/+131 | |
implementation, and segregate instrumentation concerns |