{
  "context": "Evaluating a Coralogix support response for this user question:\n\nWe set up the Coralogix Linux host integration with a filelog receiver. To route logs from different files to different Coralogix subsystems, we added an operator that sets cx.application.name and cx.subsystem.name as resource attributes on each log record. The operators are definitely running — we can see the attributes in the debug exporter output. But all logs arrive in Coralogix under the global application_name and subsystem_name values hardcoded in the exporter block. The per-file attributes are completely ignored. What's wrong?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-application-name-attributes",
      "description": "The response contains \"application_name_attributes\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-subsystem-name-attributes",
      "description": "The response contains \"subsystem_name_attributes\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "no-says-to-rename-the-operator-output-keys-or",
      "description": "Explains that the coralogix exporter only does dynamic resource-attribute routing when application_name_attributes and subsystem_name_attributes are explicitly listed in the exporter config — and that a hardcoded application_name value takes precedence over the attribute lookup unless the attributes list is configured. The fix is to add application_name_attributes: [cx.application.name] (and the subsystem equivalent) to the exporter block. A response that says to rename the operator output keys, or that focuses only on \"set the resource attribute\" without mentioning these two exporter fields, is a FAIL.",
      "max_score": 2
    }
  ]
}