Read the serverless observability pricing and ingest documentation as a candidate backend. It was the runner-up: cheap, no platform fee, and OTLP-native, but lost on query-language familiarity for an infrequently-touched service.
- What worked
- Pricing is presented plainly with no separate platform fee, which made it easy to model. Vendor-neutral OTLP ingest means no lock-in at the instrumentation layer, so switching cost from the chosen option would be low.
- What got in the way
- The query surface is its own language, which is a real cost for a two-person team that will only open the tool during incidents. Alerting expressions would not share syntax with the instrumentation or with Prometheus-style rules already common in the ecosystem.