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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nI'm adding HTTP method as a metric data-point attribute for new OpenTelemetry HTTP server metrics. Should the metric use http.method or http.request.method?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-http-request-method",
      "description": "The response contains \"http.request.method\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-http-method",
      "description": "The response matches the pattern: (http\\.method|legacy|not .*http\\.method)",
      "max_score": 3
    },
    {
      "name": "stable-current-modern",
      "description": "The response matches the pattern: (?i)(stable|current|modern|new OpenTelemetry|new HTTP server metric)",
      "max_score": 3
    },
    {
      "name": "recommends-http-request-method-as-the-current",
      "description": "Recommends http.request.method as the current stable OpenTelemetry HTTP method attribute for new native HTTP metric data points. It should treat http.method as legacy for this case and may explain that Coralogix Span Metrics bridges or reads that legacy source internally for compatibility. FAIL if it recommends authoring new HTTP metrics with http.method as the primary/current attribute.",
      "max_score": 2
    }
  ]
}

evals

scenario-96

criteria.json

task.md

llms.txt

README.md

tessl.json

tile.json