aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorzvkemp <zvkemp@gmail.com>2018-10-05 14:02:39 -0700
committerzvkemp <zvkemp@gmail.com>2018-10-05 14:10:02 -0700
commit881f4f38d44fb56db48ecd5683ebfffcc8fc284e (patch)
tree22f3c146cd3e627e43120843122dd2147dbed89b /guides
parent251b9d4bd62bfc076969bd0751fa4cc6e95a4f33 (diff)
downloadrails-881f4f38d44fb56db48ecd5683ebfffcc8fc284e.tar.gz
rails-881f4f38d44fb56db48ecd5683ebfffcc8fc284e.tar.bz2
rails-881f4f38d44fb56db48ecd5683ebfffcc8fc284e.zip
clarify role of unique_id in ActiveSupport::Notifications
Diffstat (limited to 'guides')
-rw-r--r--guides/source/active_support_instrumentation.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/guides/source/active_support_instrumentation.md b/guides/source/active_support_instrumentation.md
index 9963125fa2..64db141381 100644
--- a/guides/source/active_support_instrumentation.md
+++ b/guides/source/active_support_instrumentation.md
@@ -623,7 +623,7 @@ The block receives the following arguments:
* The name of the event
* Time when it started
* Time when it finished
-* A unique ID for this event
+* A unique ID for the instrumenter that fired the event
* The payload (described in previous sections)
```ruby
@@ -672,7 +672,8 @@ Creating custom events
Adding your own events is easy as well. `ActiveSupport::Notifications` will take care of
all the heavy lifting for you. Simply call `instrument` with a `name`, `payload` and a block.
The notification will be sent after the block returns. `ActiveSupport` will generate the start and end times
-as well as the unique ID. All data passed into the `instrument` call will make it into the payload.
+and add the instrumenter's unique ID. All data passed into the `instrument` call will make
+it into the payload.
Here's an example: