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
96%
Does it follow best practices?
Impact
92%
1.10xAverage score across 127 eval scenarios
Advisory
Suggest reviewing before use
{
"context": "Evaluating a Coralogix support response for this user question:\n\nWe run SDK head sampling at 10% before spans reach the collector, and then use the spanmetrics connector to power APM RED metrics. Traces are sampled, but we expected Span Metrics to still have full request, error, and latency coverage. Is that expectation correct?",
"type": "weighted_checklist",
"checklist": [
{
"name": "spanmetrics-span-metrics",
"description": "The response matches the pattern: (?i)(spanmetrics|Span Metrics)",
"max_score": 3
},
{
"name": "all-spans-every",
"description": "The response matches the pattern: (100%|all spans|every span)",
"max_score": 3
},
{
"name": "before-sampling-sampling",
"description": "The response matches the pattern: (?i)(before.*sampling|sampling.*before|head sampling)",
"max_score": 3
},
{
"name": "undercount-sampled-spans",
"description": "The response matches the pattern: (?i)(undercount|sampled spans|not full coverage)",
"max_score": 3
},
{
"name": "explains-that-span-metrics-only-has-full-red",
"description": "Explains that Span Metrics only has full RED coverage if the spanmetrics connector receives 100% of spans. SDK head sampling is source-side loss: sampled-out spans never reach the collector, so no collector placement can recover them; for collector-side sampling, the sampler must run after spanmetrics. If spanmetrics only sees sampled spans, the generated calls, errors, and duration metrics undercount real traffic. FAIL if it says spanmetrics always has full coverage whenever traces are sampled, regardless of where sampling happens.",
"max_score": 2
},
{
"name": "no-says-spanmetrics-can-run-before-sdk-head-s",
"description": "Does not recommend fixing SDK head sampling by running the collector spanmetrics connector before SDK head sampling, and does not claim collector ordering can recover spans already sampled out by the SDK. The response should say SDK-sampled-out spans never reach the collector, so collector placement cannot recover them. Collector-side sampling guidance remains acceptable when it says the collector sampler should run after spanmetrics. FAIL if it says spanmetrics can run before SDK head sampling or claims collector placement can recover SDK-sampled-out spans.",
"max_score": 2
}
]
}.claude-plugin
.codex-plugin
.cursor-plugin
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
scenario-82
scenario-83
scenario-84
scenario-85
scenario-86
scenario-87
scenario-88
scenario-89
scenario-90
scenario-91
scenario-92
scenario-93
scenario-94
scenario-95
scenario-96
scenario-97
scenario-98
scenario-99
scenario-100
scenario-101
scenario-102
scenario-103
scenario-104
scenario-105
scenario-106
scenario-107
scenario-108
scenario-109
scenario-110
scenario-111
scenario-112
scenario-113
scenario-114
scenario-115
scenario-116
scenario-117
scenario-118
scenario-119
scenario-120
scenario-121
scenario-122
scenario-123
scenario-124
scenario-125
scenario-126
scenario-127
skills
opentelemetry
opentelemetry-collector
references
opentelemetry-instrumentation
opentelemetry-ottl