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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nWe use the Coralogix exporter with subsystem_name_attributes: [\"log.file.subsystem\"], but every record arrives tagged with the static fallback subsystem instead. The \"log.file.subsystem\" attribute is definitely set in our logs — debug exporter shows it under the log record attributes. Why isn't the exporter picking it up?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-resource",
      "description": "The response contains \"resource\" (case-insensitive).",
      "max_score": 3
    },
    {
      "name": "record-span-level",
      "description": "The response matches the pattern: (record|span).*level|log[- ]record|record[- ]level",
      "max_score": 3
    },
    {
      "name": "identifies-that-subsystem-name-attributes-app",
      "description": "Identifies that subsystem_name_attributes / application_name_attributes on the Coralogix exporter only read RESOURCE-scope attributes. The attribute lives on the log record so the exporter cannot see it. Recommends either setting it at resource scope at the SDK / resource / resourcedetection processor, or copying it up with OTTL. FAIL if it tells the user to rename the field in their application or to change the exporter configuration.",
      "max_score": 2
    }
  ]
}

evals

llms.txt

README.md

tessl.json

tile.json