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

opentelemetry-semantic-conventions-metric-cardinality-attribute-scope

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


Our metrics backend is overwhelmed — we're seeing tens of millions of unique time series from a single counter. The labels include user.id and request_path with the full querystring. Where do those attributes belong, and what bounded label can we use for HTTP routes on metrics instead?


evals

llms.txt

README.md

tessl.json

tile.json