Releases: getsentry/relay
Releases · getsentry/relay
0.2.6
0.2.5
Yanked release: Do not use. Turned out to contain critical regressions.
-
Rewrite of PII stripping logic. This brings potentially breaking changes to
the semantics of PII configs. Most importantly field types such as
"freeform"
and"databag"
are gone, right now there is only"container"
and"text"
. All old field types should have become an alias for"text"
,
but take extra care in ensuring your PII rules still work. -
store: Minor fixes to be closer to Python.
0.2.4
0.2.3
0.2.2
For users of relay, nothing changed at all. This is a release to test embedding
some Rust code in Sentry itself.
- store: Fix segfault when trying to process contexts.
- store: Fix trimming state "leaking" between interfaces, leading to excessive trimming.
- store: Don't serialize empty arrays and objects (with a few exceptions).
0.2.1
0.2.0
Our first major iteration on Relay has landed!
- User documentation is now hosted at https://docs.sentry.io/relay/.
- SSL support is now included by default. Just configure a TLS
identity and
you're set. - Updated event processing: Events from older SDKs are now supported. Also,
we've fixed some bugs along the line. - Introduced full support for PII stripping. See PII
Configuration for instructions. - Configure with static project settings. Relay will skip querying project
states from Sentry and use your provided values instead. See Project
Configuration for a full guide. - Relay now also acts as a proxy for certain API requests. This allows it to
receive CSP reports and Minidump crash reports, among others. It also sets
X-Forwarded-For
and includes a Relay signature header.
Besides that, there are many technical changes, including:
- Major rewrite of the internals. Relay no longer requires a special endpoint
for sending events to upstream Sentry and processes events individually with
less delay than before. - The executable will exit with a non-zero exit code on startup errors. This
makes it easier to catch configuration errors. - Removed
libsodium
as a production dependency, greatly simplifying
requirements for the runtime environment. - Greatly improved logging and metrics. Be careful with the
DEBUG
andTRACE
levels, as they are very verbose now. - Improved docker containers.