zeekayandHanzo Dev
73959e2a2c
This repo shipped Sentry's README verbatim: their wordmark hotlinked from sentry-brand.storage.googleapis.com, four screenshots served out of getsentry/sentry, their SDK index, their Discord, their Transifex. The FSL grants copying and modification. It grants no trademark rights, and none of the usual open-source licenses do. So carrying upstream's wordmark as this project's masthead was the one part of the fork that was not ours to do — de-branding is a licensing requirement here, not a style preference. LICENSE and NOTICE stay exactly as they are. Those are the parts the license does require, and they are the reason the fork is legitimate; the rebrand removes the mark and keeps the attribution, which is the whole distinction. The README now says what Sentinel is and states the one fact a reader needs: it speaks the Sentry wire protocol, so existing client SDKs report to it with nothing changed but a DSN. Co-authored-by: Hanzo Dev <[email protected]>
1.4 KiB
Sentinel
Error tracking and performance monitoring for the Hanzo cloud. Sentinel receives events from your applications, groups them into issues, and tells you which ones are new, regressed, or getting worse.
Sentinel speaks the Sentry wire protocol, so the existing ecosystem of client SDKs reports to it unchanged — a DSN pointing at your Sentinel instance is the only configuration difference. There is no Sentinel-specific SDK to adopt, and none is planned; the protocol is the interface.
Running it
The deployed image is ghcr.io/hanzoai/sentry. Deployment is declared in the
universe repository and reconciled by Hanzo CD, like every other service.
Attribution and licensing
Sentinel is a fork of Sentry by Functional
Software, Inc., used under the Functional Source License, Version 1.0, Apache
2.0 Change License (FSL-1.0-Apache-2.0). See LICENSE for the
terms and NOTICE for attribution; both are required and are kept
current.
The FSL grants no trademark rights. "Sentry" is a trademark of Functional
Software, Inc., and this project is neither affiliated with nor endorsed by them.
Upstream marks are not used as branding here — where the name appears in this
codebase it refers to the module namespace (src/sentry/), the wire protocol, or
upstream attribution, none of which are brand usage.