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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nOur default ECS Fargate sidecar has detectors [env, system] in its resourcedetection config — we copied this from our ECS EC2 daemonset. Should we add the ecs detector too or leave it out?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-ecs",
      "description": "The response contains \"ecs\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "add-enable-include",
      "description": "The response matches the pattern: (?i)(add|enable|include|is correct|works|should)",
      "max_score": 3
    },
    {
      "name": "sidecar-fargate-shares",
      "description": "The response matches the pattern: (?i)(sidecar|fargate|shares? (the )?task|awsvpc)",
      "max_score": 3
    },
    {
      "name": "says-the-ecs-detector-should-be-enabled-on-a",
      "description": "Says the `ecs` detector SHOULD be enabled on a Fargate sidecar — unlike the EC2 daemonset, the sidecar shares the task's awsvpc network namespace and the detector correctly attributes data to the right task, not to the collector. The \"remove ecs detector\" rule from ECS-EC2 daemonset mode is EC2-specific and inapplicable to Fargate sidecar.",
      "max_score": 2
    }
  ]
}

evals

scenario-5

criteria.json

task.md

llms.txt

README.md

tessl.json

tile.json