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.

98

1.13x
Quality

97%

Does it follow best practices?

Impact

99%

1.13x

Average score across 81 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-27/

opentelemetry-collector-spanmetrics-daemonset-gateway-apm-empty

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


I have spanMetrics: enabled: true in our otel-integration Helm values, and the generated ConfigMap shows the spanmetrics connector wired into the traces pipeline. Traces are visible in Coralogix Explore with correct service.name and k8s attributes. But span metrics never appear — no calls_total, no duration_ms_bucket, and the APM Service Catalog stays empty and shows the onboarding prompt. The otel-integration is deployed with a daemonset agent and a gateway. Where should I look?


evals

README.md

tile.json