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

opentelemetry-semantic-conventions-ai-center-litellm-proxy

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


A customer routes LLM traffic through LiteLLM. Coralogix traces are present, but AI Center is blank. The proxy span is name="POST /chat/completions", attributes={http.route="/chat/completions", http.request.method="POST", server.address="litellm-proxy", model="claude-3-5-sonnet"}, and it does not have gen_ai.provider.name, gen_ai.system, or gen_ai.input.messages. Should semconv fix this in the collector, or is the proxy/instrumentation missing something?


evals

llms.txt

README.md

tessl.json

tile.json