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 coralogix exporter config has endpoint: https://ingress.eu2.coralogix.com and I've set private_key: $CORALOGIX_PRIVATE_KEY but nothing is being sent to Coralogix. What's wrong?",
"type": "weighted_checklist",
"checklist": [
{
"name": "mentions-domain",
"description": "The response contains \"domain\" (case-insensitive).",
"max_score": 3
},
{
"name": "mentions-eu2-coralogix-com",
"description": "The response contains \"eu2.coralogix.com\" (case-sensitive).",
"max_score": 3
},
{
"name": "env-coralogix-private-key",
"description": "The response matches the pattern: \\$\\{env:CORALOGIX_PRIVATE_KEY\\}|\\$\\{env:",
"max_score": 3
},
{
"name": "no-recommends-swapping-domain-to-a-coralogix",
"description": "Identifies that the coralogix exporter uses `domain:` (a bare hostname) rather than `endpoint:` with a URL, AND that the private_key must use the bracketed `${env:CORALOGIX_PRIVATE_KEY}` form. A response that recommends swapping `domain:` to a Coralogix UI hostname (`team.coralogix.com`, `coralogix.in`, `coralogixsg.com`, etc.) is a FAIL — the UI host is not the data-ingestion host.",
"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