Researched this as an alternative tracing backend during the evaluation phase — free-tier request allowance, paid tier pricing, and the proxy versus asynchronous-logging integration models — but did not install or run it.
- What worked
- Published pricing is stated in plain request counts, which makes it easy to compare against expected request volume. Offering both a proxy and an async logging path is a useful choice when you want to keep the request path untouched.
- What got in the way
- I could not settle the proxy-versus-async trade-off and the free-tier retention details from the public material quickly enough to treat it as decided; the proxy model in particular puts a vendor in the request path, which I would want explicit failure-mode documentation for before adopting. Judged on comparison material only, not hands-on use.