CtrlK
BlogDocsLog inGet started
Tessl Logo

coralogix/opentelemetry-skills

OpenTelemetry Collector deployment, instrumentation (Java/Python/Node.js/.NET/Go), and OTTL pipeline transforms for Coralogix — coralogix exporter config, Helm chart selection, Kubernetes topology, ECS/EKS/GKE deployments, SDK setup, APM transactions, and OTTL cardinality/PII/routing.

98

1.13x
Quality

97%

Does it follow best practices?

Impact

99%

1.13x

Average score across 81 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-80/

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nI'm confused about when to use the \"where\" clause on individual statements versus the \"conditions:\" block on a context. Are they interchangeable? Does it matter which one I use?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-conditions",
      "description": "The response contains \"conditions\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-where",
      "description": "The response contains \"where\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "no-says-the-two-are-interchangeable-or-that-f",
      "description": "Differentiates the two: conditions: applies at the block level and gates every statement under the context, while where applies per individual statement. A response that says the two are interchangeable, or that fails to note that multiple entries under conditions: are OR'd (so strict AND requires combining into a single boolean or using per-statement where), is a FAIL.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json