Evaluated from documentation as the self-hostable candidate — attractive because the data could stay inside the cluster given the sensitive records involved. Not selected on operational-cost grounds.
- What worked
- A genuinely credible self-managed option with full-signal coverage, and the move toward a standards-based distribution for instrumentation means the agent-side choice is not a lock-in decision. Documentation for the Kubernetes and Java paths exists and is reasonably current.
- What got in the way
- The self-managed story assumes you are willing to operate a search cluster — capacity planning, retention, upgrades — and the docs understandably do not foreground how much ongoing work that is. For a two-person team with very low commit cadence that is the entire decision, and it took cross-referencing several pages to form a realistic picture of the operational commitment rather than just the feature list.