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.

Sign up for GitHub

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

Jump to bottom

Verify the structure of full OTel traces in an integration test #13034

Closed
alevenberg opened this issue Nov 3, 2023 · 1 comment
Closed

Verify the structure of full OTel traces in an integration test #13034

alevenberg opened this issue Nov 3, 2023 · 1 comment
Labels
cpp: backlog While desirable, we do not have time to work on this for the foreseeable future. cpp: opentelemetry testing type: cleanup An internal cleanup or hygiene concern.

Comments

@alevenberg
Copy link
Member

Right now, we only test for spans in unit tests.
@alevenberg alevenberg added type: cleanup An internal cleanup or hygiene concern. cpp: opentelemetry testing labels Nov 3, 2023
@alevenberg alevenberg mentioned this issue Nov 3, 2023
Merged
@dbolduc dbolduc changed the title Consider an OTel end to end integration that diffs the generated telemetry data Verify the structure of full OTel traces in an integration test Nov 16, 2023
This was referenced Nov 16, 2023
Closed
Merged
@dbolduc dbolduc mentioned this issue Dec 7, 2023
Merged
@dbolduc dbolduc added the cpp: backlog While desirable, we do not have time to work on this for the foreseeable future. label May 8, 2024
@dbolduc
Copy link
Member

dbolduc commented May 8, 2024

Would be fun, but we have more important things to do.

@dbolduc dbolduc closed this as completed May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cpp: backlog While desirable, we do not have time to work on this for the foreseeable future. cpp: opentelemetry testing type: cleanup An internal cleanup or hygiene concern.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dbolduc @alevenberg