What is the underlying problem you're trying to solve?

I'm trying to get a good overview of what's happening in my Kubernetes cluster using tracing (Jaeger).

Describe the ideal solution

OPA should adhere to OpenTelemetry's Semantic Conventions, and send HTTP spans with names following the pattern {method} {route}.

Describe a "Good Enough" solution

The ideal solution seems easy enough.

Additional Context

Currently, my tracing backend (Jaeger) lists operations from OPA (1.14.1) as health, HTTP POSTand v1/data while it should list GET /health, POST /status and POST /v1/data/:path. And maybe also GET /v1/data/:path. It's hard to tell at the moment.

BTW, I see the span name HTTP POST when OPA answers with 400 Bad Request. Those are client spans.