Set REMOTE_ADDR in HTTP request event payload #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Sentry event payload supports
REMOTE_ADDR
under theenv
key:The
:remote-addr
key can be added to ring requests usingring.middleware.proxy-headers
fromring/ring-headers:0.3.0
that ise.g. enabled with
(ring-defaults/wrap-defaults ,,, {:proxy true})
fromring/ring-defaults:0.3.4
.If
:remote-addr
is not present in the request, we send the empty stringand Sentry will not show this field in its web UI.