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

chore: deprecate jaeger #2675

Merged
merged 3 commits into from
Jan 18, 2024
Merged

chore: deprecate jaeger #2675

merged 3 commits into from
Jan 18, 2024

Conversation

markphelps
Copy link
Collaborator

Fixes: #2650

Copy link

codecov bot commented Jan 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (1f34dc5) 73.02% compared to head (3c04f18) 72.99%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2675      +/-   ##
==========================================
- Coverage   73.02%   72.99%   -0.03%     
==========================================
  Files          85       85              
  Lines        8326     8325       -1     
==========================================
- Hits         6080     6077       -3     
- Misses       1869     1871       +2     
  Partials      377      377              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@markphelps markphelps marked this pull request as ready for review January 18, 2024 12:57
@markphelps markphelps requested a review from a team as a code owner January 18, 2024 12:57
@@ -22,11 +22,10 @@ type TracingConfig struct {
func (c *TracingConfig) setDefaults(v *viper.Viper) error {
v.SetDefault("tracing", map[string]any{
"enabled": false,
"exporter": TracingJaeger,
"exporter": TracingOTLP,
Copy link
Contributor

Choose a reason for hiding this comment

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

Questioning this incase it wasn't considered:
Should we be simultaneously deprecating and changing the default behaviour like this?

Just wondering if there might be folks out there with solely:

tracing:
  enabled: true

That might just be relying on it talking to jaeger.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

good call. I also added a tracing section to telemetry so we can hopefully get more data about when its safe to fully remove

Copy link
Contributor

@GeorgeMac GeorgeMac left a comment

Choose a reason for hiding this comment

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

Change looks good. Open question about whether changing the default at the same time makes sense.

@markphelps markphelps requested a review from GeorgeMac January 18, 2024 14:22
@markphelps markphelps merged commit baac459 into main Jan 18, 2024
32 of 33 checks passed
@markphelps markphelps deleted the deprecate-jaeger branch January 18, 2024 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OpenTelemetry-Go Jaeger Exporter dropped by July 2023
3 participants