Auto-instrumentation lets you automatically trace common libraries such as HTTP clients, database drivers, and more without needing to modify your code. OpenTelemetry provides auto-instrumentation libraries for many popular languages, making it fast to get started with tracing.In Ruby, you can automatically instrument popular frameworks like Rails, Rack, and ActiveRecord:
Copy
Ask AI
require 'opentelemetry/sdk'require 'opentelemetry/instrumentation/all'OpenTelemetry::SDK.configure do |c| c.use_all() end
Manual instrumentation gives you full control over your traces, allowing you to create spans wherever needed. You can customize span names, attributes, and relationships to capture the most important parts of your application’s flow.You can manually create spans in your Ruby code:
Copy
Ask AI
tracer = OpenTelemetry.tracer_provider.tracer('my-service')tracer.in_span('my-operation') do |span| your application logicend
Once your application is instrumented, you need to export telemetry data. PlayerZero supports the OpenTelemetry Protocol (OTLP) over HTTP. You can configure your OpenTelemetry SDK to export traces, logs, and metrics to PlayerZero’s endpoint by setting the endpoint URL and API token.You can configure the OTLP exporter via environment variables:
Using an OpenTelemetry Collector is optional for most setups. A collector can help route telemetry to multiple destinations, perform transformations, or batch data efficiently. You might use a collector if you want to forward telemetry to both PlayerZero and another observability platform simultaneously.You can optionally route telemetry through an OpenTelemetry Collector before sending it to PlayerZero.