-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add Jaeger Agent Configuration #434
Conversation
Codecov Report
@@ Coverage Diff @@
## master #434 +/- ##
==========================================
+ Coverage 75.27% 75.48% +0.21%
==========================================
Files 120 120
Lines 7303 7338 +35
==========================================
+ Hits 5497 5539 +42
+ Misses 1542 1535 -7
Partials 264 264
Continue to review full report at Codecov.
|
@bogdandrutu this PR allows for independently configurable jaeger agent protocols as well as sets up a place for @annanay25 to add the jaeger remote sampling configuration/functionality. |
@joe-elliott - This is great! :) About jaeger remote sampling configuration, I think its best to wait to reach consensus on where the package should live, and then the configuration options can be provided either as part of the receiver or the extension. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but I am not very familiar with Jaeger receiver, so we need more reviews.
@joe-elliott please pay the coverage cost :) |
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
…t it Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
…ent and collector protocols Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
… http server Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
5bcf3b7
to
8657535
Compare
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
@tigrannajaryan thanks for the review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @joe-elliott. LGTM, just a few nit suggestions and one Q.
Signed-off-by: Joe Elliott <[email protected]>
Signed-off-by: Joe Elliott <[email protected]>
Handling of nil retrieved values by the config provider manager was causing the string "<nil>" to be used. Fixed the handling on the manager and removed the special case on the env variable.
Adds the ability to configure the Jaeger Agent protocols independently. Resolves #157.
Changes:
agent *agentapp.Agent
because the agent did not support independently configuring the http server and agent protocols.SourceFormat
to jaeger for spans ingested through the agent services.Tests pass and this has been manually tested in our internal environment.
cc @annanay25