zeekay 4679327ddc Sentinel reads the errors /v1/event lands, and takes none itself ...

The event plane folded every occurrence into event.fact, and the Sentry
module still read and wrote event.error. Its reads now select the error
signal of event.fact, mapping issue, env, origin and the severity band.

Errors enter through /v1/event only. The Sentry envelope and store
routes, DSN keys and their rotation leave the module; the consumer of
event.error files each fact through Ingest(org, product), which keeps
the issue lifecycle and returns the issues a batch created.

2026-09-30 01:15:34 -07:00

..

config_test.go

refactor: complete clickhouse->datastore debrand — zero 'clickhouse' in .go (packages/dirs/types/aliases renamed to datastore); datastore-go/v2 driver; sentry intact; hanzoai/sqlite. (3 deploy/integration dirs reference the real upstream ClickHouse server engine — flagged, not our API)

2026-07-12 18:54:57 -07:00

config.go

Let Hanzo IAM answer who the caller is

2026-09-08 23:24:35 -07:00

handler_test.go

Let Hanzo IAM answer who the caller is

2026-09-08 23:24:35 -07:00

handler.go

Sentinel reads the errors /v1/event lands, and takes none itself

2026-09-30 01:15:34 -07:00

module_test.go

Let Hanzo IAM answer who the caller is

2026-09-08 23:24:35 -07:00

module.go

Sentinel reads the errors /v1/event lands, and takes none itself

2026-09-30 01:15:34 -07:00

o11y.go

Let Hanzo IAM answer who the caller is

2026-09-08 23:24:35 -07:00

provider_test.go

Let Hanzo IAM answer who the caller is

2026-09-08 23:24:35 -07:00

provider.go

Let Hanzo IAM answer who the caller is

2026-09-08 23:24:35 -07:00