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

task.mdevals/scenario-10/

opentelemetry-collector-filelog-multiline-stacktrace-cri-logtag

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


Our Java services on Kubernetes produce stack traces that arrive in Coralogix as dozens of separate log records — one per line — instead of a single merged entry. I added multiline configuration to the filelog receiver with a line_start_pattern matching the timestamp format, but it only captures the first line of the exception and drops all the "at ..." lines. Looking at the raw /var/log/pods files, every single log line has logtag F. Why isn't the multiline config helping, and what's the right approach?


evals

README.md

tile.json