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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nMy .NET auto-instrumented service has these env vars set but no traces appear:\n  OTEL_EXPORTER_OTLP_ENDPOINT=ingress.eu1.coralogix.com:443\n  OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer myKey\nWhat am I missing?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-https",
      "description": "The response contains \"https://\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "no-only-response-identifies-otel-traces-expor",
      "description": "Identifies that OTEL_EXPORTER_OTLP_ENDPOINT is missing the https:// URI scheme — the .NET OTLP exporter requires a full URI, so the correct value is https://ingress.eu1.coralogix.com:443, not the bare host:port accepted by Python, Node.js, and Go (Java also requires https://, so do not cite Java as an example of bare host:port being valid). OTEL_TRACES_EXPORTER defaults to \"otlp\" in .NET auto-instrumentation and is NOT a root cause. FAIL only if the response identifies OTEL_TRACES_EXPORTER as the PRIMARY or SOLE root cause and does not mention the missing https:// scheme — mentioning OTEL_TRACES_EXPORTER as a secondary note is acceptable as long as the missing https:// scheme is clearly identified as the fix.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json