coralogix/opentelemetry-skills
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
component-stability.mdskills/opentelemetry/opentelemetry-collector/references/
Collector component stability
Collector components do not all have the same production readiness. The upstream Collector status is mixed, and each receiver, processor, exporter, connector, and extension documents its own stability per signal in its README. Treat stability as a deployment requirement, not a doc footnote.
Stability levels
| Level | How to answer |
|---|---|
| Development | Do not recommend for production. Use only for exploration or repros. |
| Alpha | Limited, non-critical workloads only. Configuration can change with little notice. |
| Beta | Broader usage is reasonable, but breaking changes can still happen. Read release notes before upgrades. |
| Stable | Production default. Backward compatibility is expected except for exceptional cases such as security fixes. |
| Deprecated | Avoid new deployments. Recommend migration and explain removal risk. |
| Unmaintained | Avoid unless there is no alternative and the user accepts ownership/risk. |
For components that handle multiple signals, check the stability for the exact signal the user is using. A component can be stable for traces and less mature for logs, metrics, or profiles.
Answer pattern
When the user asks whether a component is safe to deploy:
- Ask or infer the collector version, distribution, component name, signal, and workload criticality.
- Tell them to check the component README stability table for that exact version/signal.
- If the component is alpha, say it is not the default recommendation for business-critical production traffic.
- If they still need it, require a pinned collector version, staging test with representative traffic, rollback plan, and release-note review before upgrades.
- Offer the nearest stable path when one exists, even if it is less feature-rich.
What validation does not prove
otelcol validate and a successful startup prove that YAML parses and components can be
constructed. They do not prove production stability, backward compatibility, safe
upgrade behavior, or acceptable operational risk. Do not call a production plan safe
only because the config validates.
Common Coralogix-facing examples
- A customer wants a newly released contrib processor for production URL or span-name sanitization. Check the processor README stability and qualify alpha/beta risk before recommending it broadly.
- A collector image bump pulls in a component with changed config or startup validation.
Read the component release notes and chart compatibility before telling the user to
override only
image.tag. - A user points at an OpenTelemetry specification page marked stable, but the language SDK package or Collector component they need is alpha. The implementation maturity is what matters for the recommendation.
.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