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

opentelemetry-semantic-conventions-javaagent-http-vs-jmx

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


A customer installed the OpenTelemetry Javaagent for Tomcat and asks why they only see HTTP server metrics with http.request.method, http.response.status_code, and http.route, not Tomcat thread pool or JMX runtime metrics. Is this a semantic convention problem?


evals

llms.txt

README.md

tessl.json

tile.json