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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nOur Windows host in K8s is running coralogixrepo/opentelemetry-collector-contrib-windows:0.92.0 (from the otel-integration opentelemetry-agent-windows sub-preset). We want Fleet Management. When we add extensions: [opamp] to the config, the collector refuses to start. What are our options?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "bump-upgrade-newer",
      "description": "The response matches the pattern: (?i)(bump|upgrade|newer|v?0\\.13[0-9]|older|version|image (tag|pin))",
      "max_score": 3
    },
    {
      "name": "supervisor-wrapper-binary",
      "description": "The response matches the pattern: (?i)(-Supervisor|supervisor (wrapper|binary|service)|opampsupervisor)",
      "max_score": 3
    },
    {
      "name": "no-claims-windows-doesn-t-support-opamp-at-al",
      "description": "Says the pinned 0.92.0 Windows image is too old for the `opamp` extension and recommends either bumping the image to a current Windows build that includes `opamp`, OR using the `-Supervisor` wrapper (opampsupervisor as a separate Windows service). A response that claims Windows doesn't support OpAMP at all is a FAIL — modern Windows builds do support it.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json