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

opentelemetry-semantic-conventions-spanmetrics-daemonset-pod-dimension

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


We run the OTel Collector as a Kubernetes DaemonSet with one agent per node. A service has pods on several nodes, and its Span Metrics counters look like multiple writers are colliding for the same service_name. Should k8s.pod.name be a spanmetrics dimension only if there are multiple collectors on one node, or can the normal one-agent-per-node topology need it too?


evals

llms.txt

README.md

tessl.json

tile.json