{
  "context": "Evaluating a Coralogix support response for this user question:\n\nI'm reviewing my Python programmatic instrumentation. Here's my exporter setup:\n  headers = {\n      'Authorization': 'Bearer myKey',\n      'CX-Application-Name': 'myapp',\n  }\n  exporter = OTLPSpanExporter(endpoint='ingress.eu1.coralogix.com:443', headers=headers)\nWhat's wrong with this?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-sequence",
      "description": "The response contains \"sequence\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-dict",
      "description": "The response contains \"dict\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-lowercase",
      "description": "The response contains \"lowercase\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-cx-subsystem-name",
      "description": "The response contains \"cx.subsystem.name\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "no-if-it-misses-both-the-dict-shape-and-the-k",
      "description": "Identifies at least two of these three issues (all three is ideal): (1) headers is a dict — must be a sequence of (key, value) tuples; (2) gRPC/HTTP2 requires lowercase header keys — CX-Application-Name is rejected with \"Illegal header key\"; recommend resource attributes cx.application.name and cx.subsystem.name instead; (3) cx.subsystem.name is missing (may be bundled into issue 2 as an acceptable combined fix — that counts). FAIL if it misses both the dict shape AND the key-case issue, or if it says the \"Bearer myKey\" value is wrong (a literal space is correct for programmatic tuple headers — %20 encoding only applies to the OTEL_EXPORTER_OTLP_HEADERS env var).",
      "max_score": 2
    }
  ]
}