{
  "context": "Evaluating a Coralogix support response for this user question:\n\nOur fleet has a mix of old and new OpenTelemetry instrumentation libraries. Some spans come in with http.method and http.status_code (v1 semconv), others with http.request.method and http.response.status_code (v2). Our dashboards expect v2 attribute names. How do I write OTTL that normalizes the old v1 names to v2 without overwriting spans that already have v2?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-http-request-method",
      "description": "The response contains \"http.request.method\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-set",
      "description": "The response contains \"set(\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "no-copies-v1-into-v2-unconditionally-or-that",
      "description": "Guards each set() with a where clause that checks the v2 destination is nil — e.g. where attributes[\"http.request.method\"] == nil — so spans that already have v2 attributes are not overwritten. A response that copies v1 into v2 unconditionally, or that only guards on the v1 source being present without also checking the v2 destination is empty, is a FAIL.",
      "max_score": 2
    }
  ]
}