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

[receiver/kafkareceiver] support zipkin_json(v1) #17186

Closed

Conversation

Subhasish-Behera
Copy link

Description:

changes made are :
zipkin_unmarshaler.go
    1. added new function newZipkinJSONv1Unmarshaler
    2. added const zipkinJSONv1Encoding 
zipkin_marshaler_test.go
    1. commented possible test
unmarshaler.go
    1.added zipkinJSONv1 to defaultTracesUnmarshalers() 
unmarshaler_test.go
    1.updated tests

Link to tracking Issue:
#14472
Testing:

Documentation:

changes made are
zipkin_unmarshaler.go
1. added new function newZipkinJSONv1Unmarshaler
2. added const zipkinJSONv1Encoding
zipin_marshaler_test.go
1.commented possible changes
unmarshaler.go
1.added zipkinJSONv1 to defaultTracesUnmarshalers()
unmarshaler_test.go
1.updated tests
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Dec 21, 2022

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: Subhasish-Behera / name: SUBHASISH BEHERA (639b2ca)

@runforesight
Copy link

runforesight bot commented Dec 21, 2022

Foresight Summary

    
Major Impacts

build-and-test duration(24 minutes 43 seconds) has decreased 33 minutes 43 seconds compared to main branch avg(58 minutes 26 seconds).
View More Details

⭕  build-and-test-windows workflow has finished in 5 seconds (44 minutes 51 seconds less than main branch avg.) and finished at 28th Dec, 2022.


Job Failed Steps Tests
windows-unittest-matrix -     🔗  N/A See Details
windows-unittest -     🔗  N/A See Details

✅  tracegen workflow has finished in 1 minute 1 second (2 minutes 57 seconds less than main branch avg.) and finished at 28th Dec, 2022.


Job Failed Steps Tests
build-dev -     🔗  N/A See Details
publish-latest -     🔗  N/A See Details
publish-stable -     🔗  N/A See Details

✅  check-links workflow has finished in 1 minute 25 seconds (2 minutes 10 seconds less than main branch avg.) and finished at 28th Dec, 2022.


Job Failed Steps Tests
changed files -     🔗  N/A See Details
check-links -     🔗  N/A See Details

✅  changelog workflow has finished in 2 minutes 22 seconds (5 minutes 41 seconds less than main branch avg.) and finished at 28th Dec, 2022.


Job Failed Steps Tests
changelog -     🔗  N/A See Details

✅  prometheus-compliance-tests workflow has finished in 10 minutes 58 seconds and finished at 28th Dec, 2022.


Job Failed Steps Tests
prometheus-compliance-tests -     🔗  ✅ 21  ❌ 0  ⏭ 0    🔗 See Details

❌  build-and-test workflow has finished in 24 minutes 43 seconds (33 minutes 43 seconds less than main branch avg.) and finished at 28th Dec, 2022. 2 jobs failed.


Job Failed Steps Tests
correctness-traces -     🔗  ✅ 17  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.18, internal) -     🔗  ✅ 592  ❌ 0  ⏭ 0    🔗 See Details
correctness-metrics -     🔗  ✅ 2  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.19, internal) -     🔗  ✅ 592  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.19, extension) -     🔗  ✅ 528  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.18, extension) -     🔗  ✅ 528  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.19, processor) -     🔗  ✅ 1474  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.18, processor) -     🔗  ✅ 1474  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.18, receiver-0) -     🔗  ✅ 2564  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.19, receiver-0) -     🔗  ✅ 2564  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.19, exporter) -     🔗  ✅ 2447  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.18, other) -     🔗  ✅ 4395  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.19, receiver-1) -     🔗  ✅ 1886  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.19, other) -     🔗  ✅ 4395  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.18, exporter) -     🔗  ✅ 2447  ❌ 0  ⏭ 0    🔗 See Details
integration-tests -     🔗  ✅ 55  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.18, receiver-1) -     🔗  ✅ 1886  ❌ 0  ⏭ 0    🔗 See Details
setup-environment -     🔗  N/A See Details
lint-matrix (receiver-0) Lint     🔗  N/A See Details
lint-matrix (receiver-1) -     🔗  N/A See Details
lint-matrix (processor) -     🔗  N/A See Details
lint-matrix (exporter) -     🔗  N/A See Details
lint-matrix (extension) -     🔗  N/A See Details
lint-matrix (internal) -     🔗  N/A See Details
lint-matrix (other) -     🔗  N/A See Details
check-collector-module-version -     🔗  N/A See Details
checks -     🔗  N/A See Details
check-codeowners -     🔗  N/A See Details
build-examples -     🔗  N/A See Details
lint Interpret result     🔗  N/A See Details
unittest (1.19) -     🔗  N/A See Details
unittest (1.18) -     🔗  N/A See Details
windows-msi -     🔗  N/A See Details
build-package -     🔗  N/A See Details
publish-stable -     🔗  N/A See Details
publish-check -     🔗  N/A See Details
publish-dev -     🔗  N/A See Details
cross-compile -     🔗  N/A See Details

✅  load-tests workflow has finished in 28 minutes 57 seconds (⚠️ 11 minutes 39 seconds more than main branch avg.) and finished at 28th Dec, 2022.


Job Failed Steps Tests
loadtest (TestIdleMode) -     🔗  ✅ 1  ❌ 0  ⏭ 0    🔗 See Details
loadtest (TestTraceAttributesProcessor) -     🔗  ✅ 3  ❌ 0  ⏭ 0    🔗 See Details
loadtest (TestTraceNoBackend10kSPS|TestTrace1kSPSWithAttrs) -     🔗  ✅ 8  ❌ 0  ⏭ 0    🔗 See Details
loadtest (TestMetricResourceProcessor|TestTrace10kSPS) -     🔗  ✅ 12  ❌ 0  ⏭ 0    🔗 See Details
loadtest (TestBallastMemory|TestLog10kDPS) -     🔗  ✅ 19  ❌ 0  ⏭ 0    🔗 See Details
loadtest (TestMetric10kDPS|TestMetricsFromFile) -     🔗  ✅ 6  ❌ 0  ⏭ 0    🔗 See Details
loadtest (TestTraceBallast1kSPSWithAttrs|TestTraceBallast1kSPSAddAttrs) -     🔗  ✅ 10  ❌ 0  ⏭ 0    🔗 See Details
setup-environment -     🔗  N/A See Details

🔎 See details on Foresight

*You can configure Foresight comments in your organization settings page.

Copy link
Contributor

@MovieStoreGuy MovieStoreGuy left a comment

Choose a reason for hiding this comment

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

There is a few extra things you'll need to do:

  • Add in a change log as an enhancement for the kafka receiver (run make chlog-new)
  • Update the README to say this is now an exported type to use.
  • Ensure the changes are part of the test.

Comment on lines +98 to +103
//{
// unmarshaler: newZipkinJSONv1Unmarshaler(),
// encoding: "zipkin_v1json",
// bytes: jsonv1Bytes,
// expected: td,
//},
Copy link
Contributor

Choose a reason for hiding this comment

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

I would prefer not having commented out code in the test, is there a reason for having this?

Comment on lines +127 to +131
//func TestUnmarshalZipkinJSONv1_error(t *testing.T) {
// p := newZipkinJSONv1Unmarshaler()
// _, err := p.Unmarshal([]byte("+$%"))
// assert.Error(t, err)
//}
Copy link
Contributor

Choose a reason for hiding this comment

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

Uncomment this and add it to the test being run.

@github-actions
Copy link
Contributor

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the Stale label Jan 12, 2023
@github-actions
Copy link
Contributor

Closed as inactive. Feel free to reopen if this PR is still being worked on.

@github-actions github-actions bot closed this Jan 27, 2023
@MovieStoreGuy
Copy link
Contributor

Hey @Subhasish-Behera ,

are you still working on this?

@Subhasish-Behera
Copy link
Author

https://cloud-native.slack.com/archives/CJFCJHG4Q/p1671807742419309?thread_ts=1671515726.873829&cid=CJFCJHG4Q
Yep,I would like to complete it but that doesn't seems possible as fromtranslator is missing from zipkinv1 unlike zipkinv2.

@Subhasish-Behera
Copy link
Author

@MovieStoreGuy ,@pavolloffay,@TylerHelmuth not sure why this PR was closed. I want to start working on the fromtranslator file(not currently present) for zipkinv1. Should I make a new branch for that or continue working on this branch?
(The @-mentions are for the assigned reviewers)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants