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

Remove tchannel between agent and collector #2115

Merged

Conversation

pavolloffay
Copy link
Member

Resolves #2105

Signed-off-by: Pavol Loffay ploffay@redhat.com

Signed-off-by: Pavol Loffay <ploffay@redhat.com>
@pavolloffay pavolloffay requested a review from a team as a code owner March 5, 2020 11:14
Signed-off-by: Pavol Loffay <ploffay@redhat.com>
Signed-off-by: Pavol Loffay <ploffay@redhat.com>
@codecov
Copy link

codecov bot commented Mar 5, 2020

Codecov Report

Merging #2115 into master will decrease coverage by 0.00%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2115      +/-   ##
==========================================
- Coverage   96.12%   96.12%   -0.01%     
==========================================
  Files         217      217              
  Lines       10541    10538       -3     
==========================================
- Hits        10133    10130       -3     
  Misses        353      353              
  Partials       55       55              

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cc283fb...53f9200. Read the comment docs.

@@ -55,11 +54,9 @@ func main() {
Namespace(metrics.NSOptions{Name: "agent"})

rOpts := new(reporter.Options).InitFromViper(v, logger)
tchanBuilder := tchannel.NewBuilder().InitFromViper(v, logger)
grpcBuilder := grpc.NewConnBuilder().InitFromViper(v)
builders := map[reporter.Type]app.CollectorProxyBuilder{
Copy link
Member

Choose a reason for hiding this comment

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

Do we need a map here now? We have just one exporter

Copy link
Member Author

Choose a reason for hiding this comment

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

It's needed for extensibility. E.g. at uber they will add custom reporters.

@@ -36,7 +36,6 @@ import (
ss "github.com/jaegertracing/jaeger/plugin/sampling/strategystore"
"github.com/jaegertracing/jaeger/plugin/storage"
"github.com/jaegertracing/jaeger/ports"
tCollector "github.com/jaegertracing/jaeger/tchannel/collector/app"
Copy link
Member

Choose a reason for hiding this comment

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

Is this issue also dealing with removing the tchannel endpoint from the collector? End user applications will not be able to send spans directly to the collector? This is a breaking change and should be documented

Copy link
Member Author

Choose a reason for hiding this comment

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

End applications are not using this port. This is used only by the agent.

CHANGELOG.md Outdated
@@ -6,6 +6,24 @@ Changes by Version

### Backend Changes
Copy link
Member

Choose a reason for hiding this comment

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

Maybe it should go in breaking changes

Signed-off-by: Pavol Loffay <ploffay@redhat.com>
@pavolloffay pavolloffay merged commit a9cdc98 into jaegertracing:master Mar 6, 2020
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.

Remove tchannel reporter from agent
3 participants