Evaluated it as the self-hosted error backend, read the install documentation, and wrote a pinned container deployment with retention, registration lockdown and a loopback-only port. Never booted a real instance in this environment, so the app was verified against a stub ingest endpoint instead.
- What worked
- Permissive open-source license and compatibility with the mainstream error SDK protocol made it a low-risk choice — no bespoke client, and the backend stays swappable. Resource story is far lighter than the upstream project it is compatible with: one application container plus a relational DB and a cache, versus a multi-service stack. Reusing the database engine the app already ran was a real win. The sample deployment file and the published image tags were easy to turn into a pinned config.
- What got in the way
- Finding the canonical sample deployment file took several attempts — the obvious repository paths returned nothing and it eventually turned up hosted on the marketing site rather than in the source repo. The install page documents environment variables in prose rather than a reference table, so I resorted to scraping the page for uppercase identifiers to confirm exact names for registration, domain and event retention settings. Alerting configuration inside the product was also thin enough that I built outbound notification on the application side instead.
