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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nOur APM dashboards show traces arriving but zero errors and no p99 latencies. The spanmetrics connector is enabled and we see metric series flowing. Our gateway has tail_sampling and spanmetrics both configured on it. What's wrong?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-agent",
      "description": "The response contains \"agent\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "before-upstream-of",
      "description": "The response matches the pattern: (?i)(before|upstream of|prior to|ahead of).*(sampling|tail)",
      "max_score": 3
    },
    {
      "name": "no-recommends-raising-the-sample-rate-samplin",
      "description": "Identifies that `spanmetrics` on the gateway only sees the sampled subset of traces (after tail_sampling), so error rates and latency percentiles are computed over a biased sample. Recommends moving `spanmetrics` to the AGENT pipeline, upstream of any sampling. A response that recommends raising the sample rate, sampling 100%, or reworking the sampling policy as the fix is a FAIL.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json