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

opentelemetry-instrumentation-dotnet-manual-sdk-https-scheme-eu1

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


I've set up .NET OpenTelemetry manual instrumentation for my eu1 service. My OTLP exporter reports 200 OK responses, so data is arriving at Coralogix. But nothing appears in the APM views — no service in the Service Catalog, no traces in Explore. My endpoint is https://ingress.eu1.coralogix.com:443. What resource attributes could cause data to arrive successfully but not appear in APM?


evals

llms.txt

README.md

tessl.json

tile.json