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-68/

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nAll my spans from our API service come in with a generic name like \"http.request\" regardless of which endpoint was called. I want to rename them to something like \"GET /users/:id\" using the HTTP method and route attributes. How do I do this with OTTL?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-concat",
      "description": "The response contains \"Concat\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "no-only-if-concat-is-in-the-wrong-context-or",
      "description": "PASS if the response uses context: span AND sets name via Concat([...], ...) built from the HTTP method and route attributes — either http.request.method + http.route (v2 semconv) or the v1 fallback http.method + http.route. The attributes are assumed to be populated by the upstream instrumentation; do NOT penalize the response for not explaining how to derive http.route from other fields, for not handling missing-route fallbacks, or for not stripping query strings. FAIL only if Concat is in the wrong context, or the method+route attribute pair is replaced with unrelated fields (e.g. http.url without any route attribute).",
      "max_score": 2
    }
  ]
}

evals

scenario-68

criteria.json

task.md

llms.txt

README.md

tessl.json

tile.json