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\nMy .NET auto-instrumented service has these env vars set but no traces appear:\n OTEL_EXPORTER_OTLP_ENDPOINT=ingress.eu1.coralogix.com:443\n OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer myKey\nWhat am I missing?",
"type": "weighted_checklist",
"checklist": [
{
"name": "mentions-https",
"description": "The response contains \"https://\" (case-insensitive).",
"max_score": 3
},
{
"name": "no-only-response-identifies-otel-traces-expor",
"description": "Identifies that OTEL_EXPORTER_OTLP_ENDPOINT is missing the https:// URI scheme — the .NET OTLP exporter requires a full URI, so the correct value is https://ingress.eu1.coralogix.com:443, not the bare host:port accepted by Python, Node.js, and Go (Java also requires https://, so do not cite Java as an example of bare host:port being valid). OTEL_TRACES_EXPORTER defaults to \"otlp\" in .NET auto-instrumentation and is NOT a root cause. FAIL only if the response identifies OTEL_TRACES_EXPORTER as the PRIMARY or SOLE root cause and does not mention the missing https:// scheme — mentioning OTEL_TRACES_EXPORTER as a secondary note is acceptable as long as the missing https:// scheme is clearly identified as the fix.",
"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