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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nI'm configuring the OpAMP supervisor for Fleet Management. Our region is eu2. My coralogix exporter is using domain: eu2.coralogix.com but the supervisor keeps getting connection refused. What should the supervisor endpoint be?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-ingress",
      "description": "The response contains \"ingress\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "https-ingress-eu2-coralogix-com",
      "description": "The response matches the pattern: https://ingress\\.eu2\\.coralogix\\.com",
      "max_score": 3
    },
    {
      "name": "mentions-opamp",
      "description": "The response contains \"opamp\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "explains-that-the-opamp-supervisor-uses-a-dif",
      "description": "Explains that the OpAMP supervisor uses a DIFFERENT endpoint from the coralogix data exporter — it needs the full URL with scheme, `https://ingress.<region>.coralogix.com`, not the bare hostname that goes in the exporter's `domain:` field.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json