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

opentelemetry-semantic-conventions-self-managed-resource-correlation

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


We copied a k8sattributes / resource / transform processor chain into our self-managed collector and export logs, metrics, and traces to the normal coralogix exporter. The k8s.* resource attributes are present on telemetry, but Infrastructure Explorer inventory is still empty. What collector path are we missing?


evals

llms.txt

README.md

tessl.json

tile.json