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.

92

1.10x
Quality

96%

Does it follow best practices?

Impact

92%

1.10x

Average score across 127 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-104/

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nOur metrics backend is overwhelmed — we're seeing tens of millions of unique time series from a single counter. The labels include user.id and request_path with the full querystring. Where do those attributes belong, and what bounded label can we use for HTTP routes on metrics instead?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-span",
      "description": "The response contains \"span\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-http-route",
      "description": "The response contains \"http.route\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "unbounded-bounded-low",
      "description": "The response matches the pattern: (unbounded|bounded|low[- ]cardinality|high[- ]cardinality|cardinality)",
      "max_score": 3
    },
    {
      "name": "identifies-that-user-id-and-full-url-paths-ar",
      "description": "Identifies that user.id and full URL paths are high-cardinality and belong on span attributes, not metric attributes. Recommends http.route (templated) on metrics instead of url.path. FAIL if it keeps user.id on metrics or recommends a hashing trick instead of moving to spans.",
      "max_score": 2
    }
  ]
}

evals

scenario-104

criteria.json

task.md

llms.txt

README.md

tessl.json

tile.json