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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nOur otel-integration values.yaml has spanNameReplacePattern under opentelemetry-agent.presets.spanMetrics to reduce span_name cardinality:\n\n  spanNameReplacePattern:\n    - regex: \"cycle-(manager|rpa-manager)\\\\.[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}_(.+)\"\n      replacement: \"cycle-$1.$2\"\n\nhelm upgrade fails with: \"processors::transform/span_name: statement has invalid syntax: 1:28: invalid quoted string ... invalid syntax\". The regex itself works in a standalone regex tester. What's wrong with the values file?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "matches-pattern-1",
      "description": "The response matches the pattern: \\$\\$1|\\$\\$[0-9]",
      "max_score": 3
    },
    {
      "name": "single-quote",
      "description": "The response matches the pattern: (?i)single[- ]quote",
      "max_score": 3
    },
    {
      "name": "helm-template",
      "description": "The response matches the pattern: (?i)helm template",
      "max_score": 3
    },
    {
      "name": "no-fixes-only-the-yaml-quoting-without-the-es",
      "description": "Identifies TWO INDEPENDENT escape layers, not one: (a) YAML parsing — single-quote the regex string (or use a block scalar) so backslashes aren't consumed by YAML's double-quoted-string parser; and (b) the OpenTelemetry Collector's envprovider — regex backreferences `$1` / `$2` must be written `$$1` / `$$2` in values.yaml because at collector startup the envprovider expands `$...` references, and `$$` is the literal-`$` escape. Correct attribution matters: Helm's template engine passes `$` through unchanged, so an answer that blames Helm for the `$$` rule is incorrect even if its fix (`$$1`) is right. Recommends running `helm template ... -f values.yaml` before `helm upgrade` to verify the rendered OTTL. A response that fixes only the YAML quoting without the `$$` escape, that blames the regex as syntactically invalid, that attributes the `$$` rule to Helm rather than the collector's envprovider, or that tells the user to rewrite the regex without backreferences, is a FAIL.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json