Read the official OpenTelemetry distribution and Kubernetes setup documentation to assess this as a candidate backend. The vendor-maintained OTel distribution is genuinely credible, but the documented Kubernetes onboarding path assumes operational capacity this team does not have.
- What worked
- The vendor's OpenTelemetry distribution is documented as generally available with a clear Java story, which makes it a legitimate standards-based option rather than a proprietary-agent lock-in. Kubernetes setup docs are detailed and complete.
- What got in the way
- The recommended Kubernetes path introduces an operator plus collector deployment as the default, with no prominent 'just point the app at an endpoint' alternative. For an evaluation, that made it hard to find the minimal-footprint option, and the operational surface it implies is what ruled the product out here. Hosting choices (managed vs self-run) also complicate a quick cost read.