add log exporter and metric reader params to configure azure monitor

[eavanvalkenburg]

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

This adds two additional params as kwargs to the configure_azure_monitor function.
One for log_processors, one for metric_readers, then parses them the same way as the span_processors.

Closes: #44366

If an SDK is being regenerated based on a new API spec, a link to the pull request containing these API spec changes should be included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[github-actions]

Thank you for your contribution @eavanvalkenburg! We will review the pull request and get back to you soon.

[Copilot]

Pull request overview

This PR adds extensibility to the configure_azure_monitor function by introducing two new parameters: log_processors and metric_readers. These allow users to provide custom log processors and metric readers alongside Azure Monitor's default processors/readers, following the existing pattern established by the span_processors parameter.

Key changes:

• Added LOG_PROCESSORS_ARG and METRIC_READERS_ARG constants
• Implemented default configuration handlers for the new parameters
• Integrated custom log processors and metric readers into the setup pipeline
• Added test coverage for configuration storage and defaults

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
_constants.py	Adds two new constant definitions for the log_processors and metric_readers arguments
_utils/configurations.py	Imports new constants and adds default configuration functions for log_processors and metric_readers
_configure.py	Imports new constants, updates docstring, adds logic to include custom log_processors in logger provider and custom metric_readers in meter provider
test_configurations.py	Adds test assertions for log_processors and metric_readers in configuration tests, includes whitespace cleanup
test_configure.py	Code formatting improvements (indentation, quote consistency) for existing logging tests

[Copilot]

Missing test coverage for custom log processors. While test_configurations.py verifies that log_processors are stored in configurations, there are no tests in test_configure.py that verify custom log processors are actually added to the logger provider (similar to how test_setup_tracing verifies custom span processors on line 364). Add a test that verifies logger_provider.add_log_record_processor() is called with the custom log processors.

[Copilot]

Missing test coverage for custom metric readers. While test_configurations.py verifies that metric_readers are stored in configurations, there are no tests in test_configure.py that verify custom metric readers are actually passed to the MeterProvider (similar to how test_setup_tracing verifies custom span processors on line 364). Add a test that verifies MeterProvider() is called with both the default reader and custom metric readers in the metric_readers parameter.

[Copilot]

Misleading documentation: The description for metric_readers states they "process every metric prior to exporting" and "will be run sequentially", which is inaccurate. Unlike SpanProcessors and LogRecordProcessors, MetricReaders are responsible for pulling/reading metrics from the SDK and pushing them to exporters, not processing them sequentially. Consider revising to: "List of MetricReader objects to read and export metrics. Each reader can have its own exporter and collection interval."

Suggested change

	to process every metric prior to exporting. Will be run sequentially.
	to read and export metrics. Each reader can have its own exporter and collection interval.

[github-actions]

API Change Check

APIView identified API level changes in this PR and created the following API reviews

azure-monitor-opentelemetry

[rads-1996]

@eavanvalkenburg Thank you for your contribution. Do you mind if I push some changes to this PR?