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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nWe have multiple gateway collectors behind a load balancer. Tail sampling and spanmetrics run on the gateways, and spans from one trace can hit different gateways. Which topology issue should I call out before blaming semantic attributes?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "traceid-trace-id",
      "description": "The response matches the pattern: (?i)(traceID|trace ID)",
      "max_score": 3
    },
    {
      "name": "load-balanc-routingkey",
      "description": "The response matches the pattern: (?i)(load[- ]?balanc|routingKey|traceID load balancing)",
      "max_score": 3
    },
    {
      "name": "identifies-the-topology-issue-trace-aware-pro",
      "description": "Identifies the topology issue: trace-aware processing such as tail sampling and often spanmetrics should use traceID routing so spans of a trace reach the same gateway. It may hand off exact load-balancing exporter configuration to opentelemetry-collector, but the core answer is the traceID load-balancing / trace-aware routing topology requirement. PASS if the response concisely names traceID load balancing. FAIL if it only recommends adding span attributes or blames semantic attributes instead of topology.",
      "max_score": 2
    }
  ]
}

evals

scenario-124

criteria.json

task.md

llms.txt

README.md

tessl.json

tile.json