Targeted a self-hosted APM Server's OTLP intake as the single trace backend and relied on Kibana's APM latency-threshold rule type for the p95 alert. Designed from knowledge of the product rather than against a live instance.
- What worked
- Native OTLP intake meant no vendor agent in the app, and the built-in transaction-duration rule type already supports p95 and per-transaction-name filtering, so no custom query was needed.
- What got in the way
- Log-trace correlation requires specific field names (trace.id / span.id), which forced a Logstash rename. Rule parameter support varies by version and could not be confirmed offline.