CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.10x
Quality

96%

Does it follow best practices?

Impact

92%

1.10x

Average score across 127 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-67/

opentelemetry-ottl-semconv-v1-to-v2-normalization

You are a Coralogix support expert. A user has asked the following question:


Our fleet has a mix of old and new OpenTelemetry instrumentation libraries. Some spans come in with http.method and http.status_code (v1 semconv), others with http.request.method and http.response.status_code (v2). Our dashboards expect v2 attribute names. How do I write OTTL that normalizes the old v1 names to v2 without overwriting spans that already have v2?


evals

llms.txt

README.md

tessl.json

tile.json