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.

98

1.13x
Quality

97%

Does it follow best practices?

Impact

99%

1.13x

Average score across 81 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-1/

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nMy coralogix exporter config has endpoint: https://ingress.eu2.coralogix.com and I've set private_key: $CORALOGIX_PRIVATE_KEY but nothing is being sent to Coralogix. What's wrong?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-domain",
      "description": "The response contains \"domain\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-eu2-coralogix-com",
      "description": "The response contains \"eu2.coralogix.com\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "env-coralogix-private-key",
      "description": "The response matches the pattern: \\$\\{env:CORALOGIX_PRIVATE_KEY\\}|\\$\\{env:",
      "max_score": 3
    },
    {
      "name": "no-recommends-swapping-domain-to-a-coralogix",
      "description": "Identifies that the coralogix exporter uses `domain:` (a bare hostname) rather than `endpoint:` with a URL, AND that the private_key must use the bracketed `${env:CORALOGIX_PRIVATE_KEY}` form. A response that recommends swapping `domain:` to a Coralogix UI hostname (`team.coralogix.com`, `coralogix.in`, `coralogixsg.com`, etc.) is a FAIL — the UI host is not the data-ingestion host.",
      "max_score": 2
    }
  ]
}

evals

scenario-1

criteria.json

task.md

README.md

tile.json