I've noticed deviations from the HTTP span spec.

The Node.js agent sets the span.name to the full URL path, such as GET opbeans:3000/api/products/top. This leads to the span.name having a high cardinality. That's an issue as we'd like to create metrics that have the span name as a dimension. However, it's unclear whether we'd roll up metrics for http spans in the first iteration, or only for db spans.

Also, the properties context.http.url and context.http.status_code are not populated.