You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This blog post shows how the experimental-otlp/stdout export format recently introduced in OTel Java Instrumentation (see otel-java#6675) enables a turnkey ingestion pipeline when logs can't be transported through OTLP.
Prior to experimental-otlp/stdout, practitioners had to combine painful enrichment & formatting of logs in their Java app with cumbersome parsing rules in the OTel Collector.
Outline of blog post
Problem description: the challenges to use file based logs for Java instrumentation with OTel
Solution description: OTLP/JSON logs is now a turnkey feature both in the OTel Java Instrumentation and in the OTel Collector
Reference architecture: architecture diagram including a Java app instrumented with OTel, the routing of OTel traces, metrics, and logs, and the OTel Collector pipelines
Step by step guide to setup OTLP/JSON logs through stdout coverign both the Java app and the OTel Collector
Step by step guide to do the same in Kubernetes, adding to the steps above the parsing of the container log prefixes
Conclusion
Technology used
OTel Java Instrumentation with SLF4J/Logback instrumentation and the experimental-otlp/stdout export format.
Title of the blog post
Collecting file-based Java logs with OpenTelemetry
Authors
@cyrille-leclerc, @zeitlinger
Short description of the blog post
This blog post shows how the
experimental-otlp/stdout
export format recently introduced in OTel Java Instrumentation (see otel-java#6675) enables a turnkey ingestion pipeline when logs can't be transported through OTLP.Prior to
experimental-otlp/stdout
, practitioners had to combine painful enrichment & formatting of logs in their Java app with cumbersome parsing rules in the OTel Collector.Outline of blog post
Technology used
experimental-otlp/stdout
export format.SIG
Sponsor
The text was updated successfully, but these errors were encountered: