Skip to content

Conversation

@Arunodoy18
Copy link

Adds output_paths configuration option to the debug exporter to allow users to redirect output when use_internal_logger is set to false.

Fixes #10472

Testing

All existing tests pass (5/5)
Added test cases for:
Valid output paths configuration
Invalid combinations with use_internal_logger
Empty path validation
Config marshaling/unmarshaling
Backward Compatibility
Fully backward compatible—defaults to stdout when output_paths is not specified, maintaining existing behavior.

@Arunodoy18
Copy link
Author

@andrzej-stencel - This PR adds the "output_paths" configuration option requested in #10472. Would appreciate your review when you have time. Thanks!

Copy link
Member

@andrzej-stencel andrzej-stencel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please only include in the PR the changes needed for Debug exporter?

// ConnectionPoolSize configures the number of gRPC connections to create and maintain.
// A larger pool size helps with high-throughput scenarios by distributing load across multiple connections.
// Default is 1 (single connection). Recommended for high-throughput: 4-8 connections.
ConnectionPoolSize int `mapstructure:"connection_pool_size"`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like there are some changes in this PR that should not be a part of it?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @andrzej-stencel! I've updated the PR to include only the debug exporter changes. The unrelated OTLP changes have been removed. The PR now contains only:

  • Config changes for output_paths
  • Factory logic updates
  • Tests and documentation
  • Changelog entry

Ready for re-review when you have time.

@andrzej-stencel andrzej-stencel added the exporter/debug Issues related to the Debug exporter label Jan 9, 2026
Adds output_paths config field to debug exporter, allowing users to
redirect output to stderr or file paths when use_internal_logger is false.

- Extends Config struct with OutputPaths []string field
- Updates createCustomLogger to honor configured paths (defaults to stdout)
- Adds validation to prevent use with use_internal_logger=true
- Adds validation to reject empty path values
- Updates README with new configuration option
- Adds test coverage for output_paths scenarios

Fixes open-telemetry#10472
@Arunodoy18 Arunodoy18 force-pushed the feature/debugexporter-output-paths branch from dd08eec to a6035e0 Compare January 10, 2026 06:25
@Arunodoy18
Copy link
Author

Hey, A review would be appreciated.
Cheers.

@github-actions
Copy link
Contributor

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the Stale label Jan 27, 2026
@andrzej-stencel
Copy link
Member

This PR implements the same fix as #14164, let's see if that PR is merged (it was created first).

@andrzej-stencel andrzej-stencel marked this pull request as draft January 29, 2026 09:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

exporter/debug Issues related to the Debug exporter Stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[exporter/debug] make the output stream configurable when use_internal_logger is false

2 participants