Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defining a zipkin2.reporter.Reporter results in two reporter beans as the auto-configured AsyncReporter does not back off #35455

Closed
wants to merge 1 commit into from

Conversation

be-hase
Copy link
Contributor

@be-hase be-hase commented May 17, 2023

from this PR: #35424

Modifications

ZipkinConfigurations.ReporterConfiguration

I want to use a Reporter<Span> that I created myself(bean configuration).

For some reason, the current AsyncReporter<Span> is used, so if I configure the bean by myself, two Reporter<Span> are created.

assertThat(context).hasBean("customReporter");
assertThat(context).hasSingleBean(Reporter.class);
});
this.contextRunner.withUserConfiguration(SenderConfiguration.class, CustomConfiguration.class)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

It seems that the test code was not correct because it did not include SenderConfiguration.class.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label May 17, 2023
@wilkinsona wilkinsona changed the title Fix invalid back off behavior (ZipkinConfigurations.ReporterConfigura… Defining a zipkin2.reporter.Reporter results in two reporter beans as the auto-configured AsyncReporter does not back off May 17, 2023
@wilkinsona wilkinsona added type: bug A general bug theme: observability Issues related to observability and removed status: waiting-for-triage An issue we've not yet triaged labels May 17, 2023
@wilkinsona wilkinsona added this to the 3.0.x milestone May 17, 2023
philwebb pushed a commit that referenced this pull request May 17, 2023
Update `ReporterConfiguration` so that `spanReporter` back off
if a `Reporter` bean is defined. Prior to this commit, only
`AsyncReporter` beans would be considered.

See gh-35455
@philwebb philwebb closed this in d6a1a3d May 17, 2023
@philwebb philwebb modified the milestones: 3.0.x, 3.0.7 May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme: observability Issues related to observability type: bug A general bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants