Magicians never share their secrets. But we do. Sign up for our Ruby Magic email series and receive deep insights about garbage collection, memory allocation, concurrency and much more.
Here at AppSignal we tend to be very pro-active with our support. When a 500 error occurs, we try to find out who encountered the error and contact them when the issue is resolved.
Until now we had to use cookie params and query against our database to find out who was making a request at the time an error occurred.
Starting today (with appsignal gem version ‘0.6.3’) you will be able to tag requests like this:
1 2 3 4
Appsignal.tag_request( :user => current_user.name, :email => current_user.email )
You can use this wherever the current request is accessible, we recommend calling it from a
On our exception page you can find the tags in the Overview section:
There are a couple of rules on tagging:
1 2 3 4 5 6 7 8 9
# Good Appsignal.tag_request( :user_email => 'John.email@example.com' ) # Bad Appsignal.tag_request( :user => current_user )
Tags that don’t meet these requirements will be dropped without warning. Request tagging currently only works for errors.