analytics/config
Uku Taht 2b8e3ea62a
Use finch in sentry client (#1996)
* Introduce Finch for Sentry integration

* Make sure the DummyAgent can be started

* No need to sanitize the dsn, finch takes care of that

* Simplify the dummy child spec

* Annotate redirects clause

* Make use of new `get_int_from_path_or_env`

* Actually use finch in Sentry config

* Configure `excluded_domains` correctly for Sentry

The way sentry is configured currently, when we get an HTTP error it
will be logged twice - once from Sentry.PlugCapture and once from
Sentry.LoggerBackend. The logger backend module does the right thing
by default but for some reason we've been overriding the config
parameter that by default stops double-counting errors. This commit
returns to the default configuration which is better.

* Default to 15s timeout

* Attempt to send twice at most

* Warn in sentry client

* Use warn level in sentry client

Co-authored-by: Adam Rutkowski <hq@mtod.org>
2022-07-08 11:14:52 +03:00
..
.env.dev Revert config changes 2022-05-27 15:52:31 +03:00
.env.test Allow enterprise plan users to create sites 2021-10-22 11:38:47 +02:00
config.exs added invoices section (#1511) 2021-12-09 15:49:57 +02:00
dev.exs Update dependencies 2021-10-25 11:16:56 +02:00
prod.exs New config (#595) 2021-01-13 15:41:16 +02:00
runtime.exs Use finch in sentry client (#1996) 2022-07-08 11:14:52 +03:00
test.exs Ignore unknown country code 2022-01-18 10:23:26 -06:00