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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nI'm trying to rename a metric and also change one of its per-series label values at the same time. I put both statements in a context: metric block but the label change never takes effect. What am I doing wrong?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "context-datapoint",
      "description": "The response matches the pattern: (?i)(context:? ?datapoint|datapoint context)",
      "max_score": 3
    },
    {
      "name": "no-generic-try-a-different-context-advice-wit",
      "description": "Diagnoses the root cause: metric-level edits (name, description, unit) belong in context: metric, but per-series label/attribute edits belong in context: datapoint — and putting a datapoint-level edit in a metric block causes it to silently no-op (no error). The fix is a second block with context: datapoint for the label change. Generic \"try a different context\" advice without naming metric vs datapoint explicitly is a FAIL.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json