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

opentelemetry-ottl-log-attr-to-resource-for-exporter

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


We route logs to a Coralogix subsystem using the coralogix exporter with subsystem_name_attributes: ["subsystem"]. Our application writes subsystem into the log-record attributes (attributes["log.file.subsystem"]), but the subsystem always comes back blank — the exporter can't see it. We don't want to rename the field in the application. How do I use OTTL so the exporter picks it up?


evals

llms.txt

README.md

tessl.json

tile.json