Releases and technical notes about Gotcha.
A walkthrough of the ClickHouse error “Code: 516. DB::Exception: default: Authentication failed”: the password from the package post-install prompt, the default-password.xml file, the Docker image that cuts default off from the network, the networks restriction and special characters in a DSN. How to read the real cause from the server log.
A walkthrough of the golang-migrate error “Dirty database version N. Fix and force version”: what the dirty flag means, why “just run force N” is risky, how to tell in PostgreSQL whether the migration applied, and where the traps are — CREATE INDEX CONCURRENTLY, ClickHouse, MySQL.
What to do when access to a hosted error tracker ends on somebody else's terms: what breaks immediately, how to stand up self-hosted Gotcha and swap the DSN in an evening, what cannot be migrated, and how to stop depending on an account you do not own.
What's new in Gotcha 0.4.12: operator permissions for project teams, monitor header encryption, opaque status-page addresses and ingest reliability fixes.
How to connect self-hosted Gotcha to a Tilda site: JavaScript errors and Web Vitals via an HTML block, uptime and SSL from the outside, alerts. An honest look at what a SaaS site builder makes impossible.
How to connect self-hosted Gotcha to a MODX Revolution 3 site with your own plugin: errors via a handler chain, transactions named by template, Web Vitals. Building the transport package and the full code included.
How to connect self-hosted Gotcha to an OpenCart 4 store with your own extension: PHP errors via a handler chain, transactions named by route, Web Vitals. Full code and a prebuilt archive included.
How to connect self-hosted Gotcha to a Drupal 10/11 site with your own module: errors through the stock PSR-3 logger channel, transactions named by route, Web Vitals. Full module code and a prebuilt archive included.
How to connect self-hosted Gotcha to a WordPress site with your own plugin: PHP errors (fatals included), response time per page type, JavaScript errors and Web Vitals. Full plugin code and a prebuilt zip included.
How to connect self-hosted Gotcha to a Joomla 4, 5 or 6 site with a single system plugin: PHP and JS errors, response time per component, Web Vitals, uptime, alerts and business metrics over OTLP. Full plugin code and a prebuilt zip included.
How to connect self-hosted Gotcha to a 1C-Bitrix site with your own module: PHP errors through the core's ExceptionHandlerLog, response time per script, Web Vitals. Full module code and a prebuilt archive included.
How to connect self-hosted Gotcha to an app with a Symfony backend and a separate frontend that talk over an API and live on different domains: errors, tracing, Web Vitals, uptime and alerts. Everything via env; moving to another instance is one variable change.
Gotcha's architecture: one Go binary over PostgreSQL and ClickHouse, no Kafka and no Redis. A --mode flag splits the process into ingest/web/uptime/probe or runs everything at once.
A step-by-step move from Sentry to self-hosted Gotcha: stand up an instance, swap the DSN in the same official Sentry SDK, and verify the first event. No application code changes.
What Gotcha is, why it exists, and how it's built.