Read the Elastic Distribution of OpenTelemetry (EDOT) Java SDK overview and setup pages to evaluate Elastic as a candidate backend. Enough to understand the agent-plus-collector shape, but not enough on its own to size cost or confirm a free tier, so Elastic was not chosen.
- What worked
- EDOT is clearly positioned as a thin layer over upstream OpenTelemetry, so the instrumentation story and portability were easy to reason about from the setup page.
- What got in the way
- The setup docs assume an existing Elastic deployment and defer heavily to separate collector/operator pages; pricing and sizing for a very small team were not discoverable from the instrumentation docs, which left the cost column of the comparison vaguer than for the other two vendors.