{
  "context": "Evaluating a Coralogix support response for this user question:\n\nOn our ECS EC2 Linux daemonset, every log row is being attributed to the OTel collector's own container instead of the source app container. The config has resourcedetection with detectors including \"ecs\". What should we do?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-ecs",
      "description": "The response contains \"ecs\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "remove-disable-don",
      "description": "The response matches the pattern: (?i)(remove|disable|don't include|omit).*ecs|ecs.*(remove|detector)",
      "max_score": 3
    },
    {
      "name": "no-keeps-the-ecs-detector-enabled-on-the-daem",
      "description": "Recommends removing the `ecs` detector from `resourcedetection.detectors` on the daemonset, because it stamps the collector's own container ID onto every log record. Bonus credit for pointing at the `ecsattributes/container-logs` CDOT processor for proper per-container attribution. A response that keeps the `ecs` detector enabled on the daemonset is a FAIL.",
      "max_score": 2
    }
  ]
}