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.

92

1.10x
Quality

96%

Does it follow best practices?

Impact

92%

1.10x

Average score across 127 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-9/

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nWe're running otel-integration with the Fleet Management supervisor enabled. I helm-upgraded with new processor settings in values.yaml and my changes don't seem to have taken effect. What am I missing?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-supervisor",
      "description": "The response contains \"supervisor\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "override-ing-overriden",
      "description": "The response matches the pattern: (?i)(override(s|ing|n)?|overriden|precedence|beats|wins|takes over|takes precedence|UI (config|settings)|fleet (manager|management).*config|remote[- ]?config|Fleet Manager)",
      "max_score": 3
    },
    {
      "name": "explains-that-with-presets-fleetmanagement-su",
      "description": "Explains that with `presets.fleetManagement.supervisor.enabled: true` the supervisor owns the runtime config — Fleet Manager UI settings take precedence over values.yaml, and helm-upgrading the chart has no effect on processor config. Recommends either editing the config in the Fleet Manager UI or disabling the supervisor to let Helm values take effect again.",
      "max_score": 2
    }
  ]
}

evals

scenario-9

criteria.json

task.md

llms.txt

README.md

tessl.json

tile.json