You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,6 +68,8 @@ config :sentry,
68
68
|`server_name`| False | None ||
69
69
|`use_error_logger`| False | False ||
70
70
| hackney_opts | False |[]||
71
+
| hackney_pool_max_connections | False | 50 ||
72
+
| hackney_pool_timeout | False | 5000 ||
71
73
72
74
An example production config might look like this:
73
75
@@ -113,7 +115,7 @@ Now, on our servers, we can set the environment variable appropriately. On
113
115
our local development machines, exceptions will never be sent, because the
114
116
default value is not in the list of `included_environments`.
115
117
116
-
Sentry uses the [hackney HTTP client](https://github.com/benoitc/hackney) for HTTP requests. If you need to set [hackney configurations](https://github.com/benoitc/hackney/blob/master/doc/hackney.md#request5) for things like a proxy or different pool, the `hackney_opts` configuration is passed directly to hackney.
118
+
Sentry uses the [hackney HTTP client](https://github.com/benoitc/hackney) for HTTP requests. Sentry starts its own hackney pool named `:sentry_pool` with a default connection pool of 50, and a connection timeout of 5000 milliseconds. The pool can be configured with the `hackney_pool_max_connections` and `hackney_pool_timeout` configuration keys. If you need to set other [hackney configurations](https://github.com/benoitc/hackney/blob/master/doc/hackney.md#request5) for things like a proxy, using your own pool or response timeouts, the `hackney_opts` configuration is passed directly to hackney for each request.
0 commit comments