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\nI've set up .NET OpenTelemetry manual instrumentation for my eu1 service. My OTLP exporter reports 200 OK responses, so data is arriving at Coralogix. But nothing appears in the APM views — no service in the Service Catalog, no traces in Explore. My endpoint is https://ingress.eu1.coralogix.com:443. What resource attributes could cause data to arrive successfully but not appear in APM?",
"type": "weighted_checklist",
"checklist": [
{
"name": "mentions-cx-application-name",
"description": "The response contains \"cx.application.name\" (case-sensitive).",
"max_score": 3
},
{
"name": "mentions-cx-subsystem-name",
"description": "The response contains \"cx.subsystem.name\" (case-sensitive).",
"max_score": 3
},
{
"name": "mentions-service-name",
"description": "The response contains \"service.name\" (case-sensitive).",
"max_score": 3
},
{
"name": "no-if-it-suggests-the-issue-is-in-the-endpoin",
"description": "Identifies that missing resource attributes are the cause: all three of service.name, (required for APM Service Catalog entry and transaction grouping), cx.application.name (required for data routing to the correct Coralogix team), and cx.subsystem.name (required for TCO policy and APM grouping) must be set. Data arrives (200 OK) but is not visible in APM or routed correctly when any of these are missing. FAIL if it suggests the issue is in the endpoint format or authentication, or if it omits any of the three required attributes.",
"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