{
  "context": "Evaluating a Coralogix support response for this user question:\n\nMy Node.js service injects a traceparent header into outgoing HTTP requests, but when the request reaches our .NET Framework backend I see independent spans in Coralogix instead of child spans — the trace is broken at the service boundary. What's wrong?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-propagat",
      "description": "The response contains \"propagat\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-w3c",
      "description": "The response contains \"W3C\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-addaspnetinstrumentation",
      "description": "The response contains \"AddAspNetInstrumentation\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "no-if-it-identifies-the-node-js-injection-as",
      "description": "Explains that .NET Framework does not extract incoming W3C traceparent headers automatically and requires server-side instrumentation: OpenTelemetry.Instrumentation.AspNet must be installed and AddAspNetInstrumentation() called on the TracerProvider so the server reads and continues the incoming trace context. Must NOT suggest AddHttpClientInstrumentation — that only instruments outgoing HttpClient calls and does nothing for incoming request propagation. Should also recommend confirming the upstream Node.js service sends W3C format headers (not B3/Zipkin) and that no intermediaries strip the traceparent header. FAIL if it identifies the Node.js injection as the problem, if it does not mention AddAspNetInstrumentation (or AddAspNetCoreInstrumentation for .NET Core), or if it recommends AddHttpClientInstrumentation as the fix.",
      "max_score": 2
    }
  ]
}