{
  "context": "Evaluating a Coralogix support response for this user question:\n\nMy Node.js app uses OTLPTraceExporter (HTTP/proto) with url set to 'https://ingress.eu2.coralogix.com:443'. Traces are not arriving in Coralogix and the exporter returns no errors. What is the correct endpoint URL to use, and why does the current one fail silently?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-v1-traces",
      "description": "The response contains \"/v1/traces\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-https-ingress-eu2-coralogix-com-443-v1-traces",
      "description": "The response contains \"https://ingress.eu2.coralogix.com:443/v1/traces\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "no-only-response-recommends-a-url-without-v1",
      "description": "Identifies that OTLPTraceExporter (HTTP/proto) requires the /v1/traces path suffix — the correct url is \"https://ingress.eu2.coralogix.com:443/v1/traces\". Explains that the base URL without the path sends to the wrong endpoint and gets no error because the server returns a non-export response that the SDK ignores. The critical distinction is that HTTP/proto exporters require the signal path suffix (/v1/traces) while gRPC exporters do not. The user's current URL \"https://ingress.eu2.coralogix.com:443\" is correctly cited as the WRONG URL — do not FAIL for mentioning it as the broken config. FAIL only if the response RECOMMENDS a URL without /v1/traces as the correct HTTP/proto endpoint, or if it does not mention the /v1/traces path suffix at all.",
      "max_score": 2
    }
  ]
}