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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nShould I use the OpenTelemetry Collector or send directly from my app SDK to Coralogix?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-collector",
      "description": "The response contains \"collector\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-direct",
      "description": "The response contains \"direct\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "no-if-it-recommends-one-path-without-mentioni",
      "description": "Explains the tradeoffs: direct export is simpler and good for getting started, while via-collector adds batching, retry, enrichment (k8sattributes, resource detection), and tail sampling. Does not recommend one over the other without asking about the user's context. FAIL if it recommends one path without mentioning the tradeoff.",
      "max_score": 2
    }
  ]
}

evals

scenario-27

criteria.json

task.md

llms.txt

README.md

tessl.json

tile.json