open-telemetry / open-telemetry/opentelemetry-ruby

Use the spec-recommended 10000ms default interval for the stdout exporter

Open Beginner friendly
#2,373 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug good first issue metrics spec-compliance spec:stable
Dominant language
Ruby
Stars
606
Forks
301
Avg merge
3d 19h
Merged PRs (30d)
42

Description

Spec requirement

The stdout exporter SHOULD pair with a periodic exporting MetricReader using a default exportIntervalMilliseconds of 10000 for this exporter specifically (sdk_exporters/stdout.md:40-46).

Current behavior

configurator_patch.rb:37 (permalink) wires ConsoleMetricPullExporter into a PeriodicMetricReader.new(exporter: ...) correctly, but PeriodicMetricReader's interval defaults to OTEL_METRIC_EXPORT_INTERVAL/60000 (export/periodic_metric_reader.rb:25 (permalink)), the general default — nothing special-cases the console exporter's interval to 10000ms.

Suggested fix

When wiring the console exporter's default PeriodicMetricReader in configurator_patch.rb, pass export_interval_millis: 10_000 explicitly rather than relying on the general-purpose default.

Related rows in SPEC_COMPLIANCE_METRICS.md

STDOUT-3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in metrics_sdk/lib/opentelemetry/sdk/metrics/configurator_patch.rb at the ConsoleMetricPullExporter wiring, then compare it with metrics_sdk/lib/opentelemetry/sdk/metrics/export/periodic_metric_reader.rb. Update the console exporter's default reader configuration to use a 10,000 ms interval, while leaving the general reader default unchanged; verify the STDOUT-3 requirement is satisfied.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
observability
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
88/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.