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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nCollector fails to start with: \"cannot start pipelines: failed to start resourcedetection/resource_catalog processor: can't get K8s Instance Metadata; node name is empty\". This is on a node in our daemonset. What's wrong?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "cluster-collector-cluster-collector",
      "description": "The response matches the pattern: (?i)(cluster[- ]collector|cluster.collector|deployment)",
      "max_score": 3
    },
    {
      "name": "only-instead-move",
      "description": "The response matches the pattern: (?i)(only|instead|move|remove|incorrect|wrong|not (a |on |on the )?daemonset|should (not |run on)|misplac|belongs (on|to))",
      "max_score": 3
    },
    {
      "name": "explains-that-resourcedetection-resource-cata",
      "description": "Explains that `resourcedetection/resource_catalog` (and Resource Catalog plumbing in general) belongs on the cluster-collector Deployment, not the per-node daemonset — the daemonset pod can't get node-name / K8s-instance-metadata injection. Recommends moving or removing it from the daemonset configuration.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json