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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nI need to send error spans and slow spans to a high-priority pipeline with more aggressive sampling, and send everything else to a standard pipeline. Can I do this with OTTL? Which component handles pipeline splitting?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-routing",
      "description": "The response contains \"routing\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "no-response-tells-the-user-to-achieve-the-spl",
      "description": "Names the routing connector (not the transform or filter processor, and not a second receiver) as the component that splits telemetry across pipelines based on an OTTL condition. Describes the routing mechanism concretely — either via a table: of statements keyed by OTTL condition (route() statements, or context + condition + pipelines entries) or an equivalent OTTL-conditioned split. Mentioning an explicit route() call or a table: block both pass. FAIL if the response tells the user to achieve the split with the transform processor, filter processor, tail_sampling processor, or by forking receivers.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json