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

criteria.jsonevals/scenario-101/

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nA 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?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "http-semconv-server",
      "description": "The response matches the pattern: (?i)(HTTP semconv|HTTP server metrics|http\\.request\\.method|http\\.response\\.status_code|http\\.route)",
      "max_score": 3
    },
    {
      "name": "mentions-jmx",
      "description": "The response contains \"JMX\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "explains-that-javaagent-http-semantic-convent",
      "description": "Explains that Javaagent HTTP semantic-convention metrics are not Tomcat/JMX runtime metrics, so Tomcat internals require separate JMX collection/setup such as a scraper, receiver, or instrumentation setup. PASS if it says semconv does not create Tomcat/JMX metrics and points to separate Javaagent/instrumentation/JMX setup. FAIL if it says changing HTTP semconv attributes will produce Tomcat runtime metrics.",
      "max_score": 2
    }
  ]
}

evals

scenario-101

criteria.json

task.md

llms.txt

README.md

tessl.json

tile.json