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

Fix fluentd zipkin json parsing #433

Merged
merged 2 commits into from Feb 20, 2020
Merged

Conversation

sumo-drosiek
Copy link
Contributor

Description

FIx fluent json parsing
Fix zipkin receiver port exposition

Testing performed
  • ci/build.sh
  • Redeploy fluentd and fluentd-events pods
  • Confirm events, logs, and metrics are coming in

Copy link
Contributor

@mat-rumian mat-rumian left a comment

Choose a reason for hiding this comment

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

LGTM, only the hostname instead of 0.0.0.0 could be worth to check 🍖

@@ -3,7 +3,8 @@ receivers:
jaeger:
protocols:
grpc:
zipkin: {}
zipkin:
endpoint: "0.0.0.0:9411"
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we could check if hostname name from values.yaml will work in this place.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I could use {{ printf "%s-otelcol" (include "sumologic.fullname" .) }}, but it will be easy to omit while updating collector name :)

@sumo-drosiek sumo-drosiek merged commit 266106c into master Feb 20, 2020
@sumo-drosiek sumo-drosiek deleted the drosiek-fix-fluent-json-parsing branch February 20, 2020 13:52
Copy link
Contributor

@perk-sumo perk-sumo left a comment

Choose a reason for hiding this comment

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

LGTM 👍

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.

None yet

3 participants