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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nNo traces are reaching Coralogix. I've added a transform processor with set(attributes[\"forwarded\"], true) to make sure at least something goes through, but it hasn't changed anything. Should I try a different OTTL statement?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "receiver-exporter-connectivity",
      "description": "The response matches the pattern: (?i)(receiver|exporter|connectivity|DNS|domain|egress|endpoint|private_key|credentials|network)",
      "max_score": 3
    },
    {
      "name": "no-suggests-another-ottl-statement-as-the-fix",
      "description": "Says clearly that \"no data reaching Coralogix\" is almost never an OTTL problem — it's upstream (receiver/exporter connectivity, DNS, TLS, proxy, private key, region/domain). Must tell the user to stop trying transform/OTTL statements and check the exporter and network path instead. A response that suggests another OTTL statement as the fix is a FAIL.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json