The recently published release of Gotcha 1.0 introduces a self-hosted monitoring platform that offers a comprehensive suite of features including error tracking, distributed traces, metrics, profiles, logs, availability monitoring, public status pages, and host monitoring. Developed in Go, the project is distributed under the Apache-2.0 license. Data reception is compatible with the Sentry SDK and OTLP protocol, while data is stored in PostgreSQL and ClickHouse. The minimum requirements for the platform are 2 vCPUs and 2 GB of RAM. It is worth noting that the interface, letter templates, and documentation are available in both Russian and English.
The version number 1.0 signifies that backward compatibility issues have been addressed. Changes such as the modification of environment variable names, receiving addresses, request body formats, migration directions, backup formats, outgoing webhook body, and the addresses of previously published status pages have been made in a backwards compatible manner. Anything else will be addressed in the 2.0 branch. Furthermore, three deprecated Web API addresses (/logs, /profiles/pprof, and /api/{project}/deployments/) will continue to work and will only be removed in the next major release.
Compared to previous releases (0.5-0.17), the new features added in Gotcha 1.0 include incident groups for collapsing cascading incidents into a single card, the ability to suppress notifications based on the dependency graph, ready collector configurations for PostgreSQL, nginx, Redis, Docker, and MariaDB, background uploads of errors and events in CSV, JSON, and NDJSON with personal data masking, rotation of the encryption master key without downtime, custom metrics for the reception and liveliness of background processors, a separate namespace (/api/v1/*) for receiving points and types of DSN keys that prevent unauthorized registration of hosts by revealed browser keys, and improved error handling during configuration startup.