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

opentelemetry-semantic-conventions-service-name-resource-scope

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


I'm reviewing an instrumentation PR that adds service.name to every span as a span attribute. Traces still show up in Coralogix but the team is seeing duplicate data and weird query behaviour. What's wrong, and where should service.name actually live?


evals

llms.txt

README.md

tessl.json

tile.json