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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nNone of my logs are reaching Coralogix. I've tried adding a transform processor with set(attributes[\"forwarded\"], true) to force something through, but it makes no difference. Maybe OTTL is broken in our version? How do I fix the transform so the logs get exported?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "receiver-exporter-pipeline",
      "description": "The response matches the pattern: (?i)(receiver|exporter|pipeline|connectivity|DNS|wiring)",
      "max_score": 3
    },
    {
      "name": "not-ottl-transform",
      "description": "The response matches the pattern: (?i)(\\bnot\\b.*(OTTL|transform)|OTTL.*(\\bnot\\b|\\bisn't\\b)|\\bisn't\\b.*(OTTL|transform))",
      "max_score": 3
    },
    {
      "name": "no-response-prescribes-ottl-fixes-transform-t",
      "description": "Declines to treat this as an OTTL problem and redirects to infrastructure troubleshooting — receiver connectivity, exporter endpoint/auth, pipeline wiring, or Coralogix endpoint configuration — before offering any OTTL YAML. If the response prescribes OTTL fixes (transform tweaks, different statements) as the primary answer, that is a FAIL.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json