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.

98

1.13x
Quality

97%

Does it follow best practices?

Impact

99%

1.13x

Average score across 81 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-5/

{
  "context": "Evaluating a Coralogix support response for this user question:\n\nWe've deployed the ECS EC2 CDOT daemonset. Our applications in other tasks are trying to send OTLP to localhost:4317 but nothing is being received. What are we missing?",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "node-ip-host",
      "description": "The response matches the pattern: (?i)(node[ -]ip|host[ -]ip|instance[ -]ip|169\\.254\\.169\\.254|ec2 metadata|private ip)",
      "max_score": 3
    },
    {
      "name": "host-network-hostnetwork",
      "description": "The response matches the pattern: (?i)(host[ -]?network|hostNetwork|not localhost|network namespace|different container)",
      "max_score": 3
    },
    {
      "name": "explains-that-ecs-tasks-each-get-their-own-ne",
      "description": "Explains that ECS tasks each get their own network namespace, so an app in one task cannot reach the daemonset over `localhost` — apps must target the EC2 host IP (obtainable from the instance metadata service at 169.254.169.254, or the task-level environment), and the CDOT daemonset must run with `networkMode: host` / `hostNetwork`.",
      "max_score": 2
    }
  ]
}

evals

README.md

tile.json