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
97%
Does it follow best practices?
Impact
99%
1.13xAverage score across 81 eval scenarios
Advisory
Suggest reviewing before use
{
"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
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
scenario-42
scenario-43
scenario-44
scenario-45
scenario-46
scenario-47
scenario-48
scenario-49
scenario-50
scenario-51
scenario-52
scenario-53
scenario-54
scenario-55
scenario-56
scenario-57
scenario-58
scenario-59
scenario-60
scenario-61
scenario-62
scenario-63
scenario-64
scenario-65
scenario-66
scenario-67
scenario-68
scenario-69
scenario-70
scenario-71
scenario-72
scenario-73
scenario-74
scenario-75
scenario-76
scenario-77
scenario-78
scenario-79
scenario-80
scenario-81
skills
opentelemetry
opentelemetry-collector
references
opentelemetry-instrumentation
opentelemetry-ottl