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

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nWe need to mask PII in our logs before they leave the collector. We want to hash user IDs so we can still correlate without exposing them, mask credit card numbers in the log message field, and redact Authorization header values in span attributes. How do I do each of these with OTTL?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "mentions-sha256",
      "description": "The response contains \"SHA256\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "mentions-replace-pattern",
      "description": "The response contains \"replace_pattern\" (case-sensitive).",
      "max_score": 3
    },
    {
      "name": "no-suggest-deleting-the-fields-outright-when",
      "description": "Maps each PII requirement to the right OTTL primitive: SHA256 for the user ID (correlation-preserving hashing), replace_pattern or replace_all_patterns for card numbers in the body, and replace_pattern for the Authorization header value in span attributes. Does not suggest deleting the fields outright when the user asked for masking/hashing.",
      "max_score": 2
    }
  ]
}

evals

scenario-63

criteria.json

task.md

llms.txt

README.md

tessl.json

tile.json