{
  "context": "Evaluating a Coralogix support response for this user question:\n\nAfter upgrading opentelemetry-collector-contrib from 0.140 to 0.144, our collector fails to start with: \"Error: exporters::coralogix: profiles signal is not supported with HTTP protocol, use gRPC protocol (default) instead\". We have protocol: http set in our coralogix exporter config, but we are not sending profiles — only logs, metrics, and traces. The same config worked fine on 0.140. What changed and how do we fix it?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-profiles",
      "description": "The response contains \"profiles\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "grpc-remove-protocol",
      "description": "The response matches the pattern: (?i)(grpc|remove.*protocol|protocol.*grpc|drop.*http)",
      "max_score": 3
    },
    {
      "name": "no-says-to-add-a-profiles-pipeline-or-that-sa",
      "description": "Explains that v0.144 added profiles support to the coralogix exporter, and the exporter now validates HTTP compatibility for ALL signals at startup — not just signals in active pipelines — so protocol: http fails even with no profiles pipeline. The fix is to remove protocol: http (gRPC is the default and the only supported transport for profiles). A response that says to add a profiles pipeline, or that says to downgrade the collector version, is a FAIL.",
      "max_score": 2
    }
  ]
}