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

An industry standard issue about using OpenTelemetry #5346

Closed
EkkoLee98 opened this issue Jan 15, 2025 · 2 comments
Closed

An industry standard issue about using OpenTelemetry #5346

EkkoLee98 opened this issue Jan 15, 2025 · 2 comments
Labels

Comments

@EkkoLee98
Copy link

EkkoLee98 commented Jan 15, 2025

Dear All
I have an industry standard issue about using OpenTelemetry.

Should I use the same Trace to report telemetry data on a page, or should each operation (including interface requests) have a different Trace?

### eg1: All operations on a page(including interface requests) as a span belong to trace.

Image

### eg2: One operation corresponds to one trace.

Image

(The above images are sourced from uptrace😄)

I would greatly appreciate it if you could offer some advice on how to follow industry standards when using OpenTelemetry. Thank you so much for your help! 🙏

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the stale label Mar 17, 2025
Copy link

This issue was closed because it has been stale for 14 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant