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-123/

opentelemetry-semantic-conventions-spanmetrics-status-code-value-mapping

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


With spanmetrics.statusCodeConvention.useOtelPrefix enabled, the collector debug exporter shows generated metric datapoints with otel.status_code=ERROR and OK, while unset datapoints have no otel.status_code attribute. The old raw datapoints used status.code=Error, Ok, and Unset, while Prometheus labels may show STATUS_CODE_ERROR. Which raw values or absence checks should a collector-side metrics bridge match?


evals

llms.txt

README.md

tessl.json

tile.json