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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nOur memory_limiter processor is firing constantly. The collector's own process.runtime.go.mem.heap_alloc shows 49 MiB but kubectl top pod shows 464 MiB. Is this a memory leak?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "page-cache",
      "description": "The response matches the pattern: (?i)page[ -]?cache",
      "max_score": 3
    },
    {
      "name": "explains-that-the-49-mib-go-heap-vs-464-mib-c",
      "description": "Explains that the 49 MiB Go heap vs 464 MiB container RSS gap is kernel page cache (from hostPath /var/log/pods mounts counted toward the container's cgroup memory), NOT a Go memory leak. Says clearly this is not a leak and walks through how to confirm via the collector's own `process.runtime.go.mem.*` self-telemetry.",
      "max_score": 2
    }
  ]
}

evals

scenario-20

criteria.json

task.md

README.md

tile.json