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

Add standard tags for internal warnings and span format #6524

Merged
merged 6 commits into from
Jan 11, 2025

Conversation

ADI-ROXX
Copy link
Contributor

@ADI-ROXX ADI-ROXX commented Jan 11, 2025

Which problem is this PR solving?

Description of the changes

  • Replaced the names of non-standard tags with standard tags

How was this change tested?

  • make test returned pass for all the test cases

Checklist

@ADI-ROXX ADI-ROXX requested a review from a team as a code owner January 11, 2025 11:57
@ADI-ROXX ADI-ROXX requested a review from jkowall January 11, 2025 11:57
Signed-off-by: cs-308-2023 <adityaruhela2003@gmail.com>
@yurishkuro
Copy link
Member

Please read contributing.md for how pr titles should be written.

@ADI-ROXX ADI-ROXX changed the title [WIP] Added standard tags for jaeger.internal.warnings and internal.span.format [WIP] Add Standard Tags for Internal Warnings and Span Format Jan 11, 2025
Signed-off-by: cs-308-2023 <adityaruhela2003@gmail.com>
Signed-off-by: cs-308-2023 <adityaruhela2003@gmail.com>
Signed-off-by: cs-308-2023 <adityaruhela2003@gmail.com>
@yurishkuro yurishkuro changed the title [WIP] Add Standard Tags for Internal Warnings and Span Format [WIP] Add standard tags for internal warnings and span format Jan 11, 2025
@yurishkuro yurishkuro changed the title [WIP] Add standard tags for internal warnings and span format Add standard tags for internal warnings and span format Jan 11, 2025
@yurishkuro yurishkuro enabled auto-merge (squash) January 11, 2025 18:07
Copy link

codecov bot commented Jan 11, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.25%. Comparing base (ef4b968) to head (1c99d59).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6524      +/-   ##
==========================================
- Coverage   96.29%   96.25%   -0.04%     
==========================================
  Files         372      372              
  Lines       21278    21278              
==========================================
- Hits        20489    20481       -8     
- Misses        603      609       +6     
- Partials      186      188       +2     
Flag Coverage Δ
badger_v1 10.68% <ø> (ø)
badger_v2 2.78% <ø> (ø)
cassandra-4.x-v1-manual 16.58% <ø> (ø)
cassandra-4.x-v2-auto 2.71% <ø> (ø)
cassandra-4.x-v2-manual 2.71% <ø> (ø)
cassandra-5.x-v1-manual 16.58% <ø> (ø)
cassandra-5.x-v2-auto 2.71% <ø> (ø)
cassandra-5.x-v2-manual 2.71% <ø> (ø)
elasticsearch-6.x-v1 20.25% <ø> (ø)
elasticsearch-7.x-v1 20.33% <ø> (ø)
elasticsearch-8.x-v1 20.49% <ø> (+<0.01%) ⬆️
elasticsearch-8.x-v2 2.78% <ø> (+<0.01%) ⬆️
grpc_v1 12.20% <ø> (ø)
grpc_v2 9.04% <ø> (ø)
kafka-3.x-v1 10.36% <ø> (ø)
kafka-3.x-v2 2.78% <ø> (ø)
memory_v2 2.78% <ø> (+<0.01%) ⬆️
opensearch-1.x-v1 20.38% <ø> (+<0.01%) ⬆️
opensearch-2.x-v1 20.38% <ø> (ø)
opensearch-2.x-v2 2.77% <ø> (ø)
tailsampling-processor 0.51% <ø> (ø)
unittests 95.13% <100.00%> (-0.04%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@ADI-ROXX
Copy link
Contributor Author

@yurishkuro Can you give some ideas how to resolve the lint issues. I am not able to understand why they're arising.

@yurishkuro
Copy link
Member

need to run make fmt

Signed-off-by: cs-308-2023 <adityaruhela2003@gmail.com>
auto-merge was automatically disabled January 11, 2025 18:28

Head branch was pushed to by a user without write access

@yurishkuro yurishkuro enabled auto-merge (squash) January 11, 2025 18:40
@yurishkuro yurishkuro merged commit 1379a97 into jaegertracing:main Jan 11, 2025
54 checks passed
@yurishkuro
Copy link
Member

Thanks!

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.

Standardize on internal tag/attribute naming as @jaeger@something
3 participants