{
  "context": "Evaluating a Coralogix support response for this user question:\n\nHow do I instrument a Go application to send metrics and traces to Coralogix ap2 region?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-ingress-ap2-coralogix-com-443",
      "description": "The response contains \"ingress.ap2.coralogix.com:443\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-credentials-newtls-nil",
      "description": "The response contains \"credentials.NewTLS(nil)\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-cx-application-name",
      "description": "The response contains \"cx.application.name\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-coralogix-api-key",
      "description": "The response contains \"CORALOGIX_API_KEY\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "no-if-it-recommends-go-auto-instrumentation-o",
      "description": "Covers Go manual instrumentation (code or detailed prose both acceptable) with: TLS credentials (credentials.NewTLS(nil)) on all exporters, an Authorization header map (\"Bearer \" + token — note literal space), the coralogix-opentelemetry-go sampler for APM transactions, and the endpoint ingress.ap2.coralogix.com:443 without an https:// scheme in the gRPC dial options. FAIL if it recommends Go auto-instrumentation, omits credentials.NewTLS(nil), or uses https:// in the gRPC endpoint.",
      "max_score": 2
    }
  ]
}