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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nI'm trying to clean up span names with a transform processor's replace_pattern, but the collector refuses to start and logs: \"statement has invalid syntax: 1:28: invalid quoted string '\\\"cycle-(manager|rpa-manager)\\\\\\\\.[0-9a-f]{8}-[0-9a-f]{4}-...\\\"': invalid syntax\". My regex works fine in a regex tester. What's wrong with how I'm writing it in the YAML?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-replace-pattern",
      "description": "The response contains \"replace_pattern\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "escap-quot-backslash",
      "description": "The response matches the pattern: (?i)(escap|quot|backslash|yaml)",
      "max_score": 3
    },
    {
      "name": "explains-that-the-error-is-not-an-ottl-bug-or",
      "description": "Explains that the error is NOT an OTTL bug or a bad regex, but a YAML+OTTL quoting collision: the regex has to be a valid OTTL string literal AND a valid YAML scalar. Suggests a concrete fix — most commonly using single quotes on the outside (YAML) with double quotes as the OTTL string delimiter, or using a YAML block scalar (|- or >-), or doubling the backslashes to survive both parsing layers. Avoids vague \"check your escaping\" without a working example.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json