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

[ENHANCEMENT] Allow dataset (e.g. traces) creation to provide span_id links back to the original trace #4392

Open
mikeldking opened this issue Aug 26, 2024 · 1 comment
Labels
enhancement New feature or request stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed

Comments

@mikeldking
Copy link
Contributor

mikeldking commented Aug 26, 2024

Right now you can download traces as a dataset, and then upload it as the "pure" dataset but the link to the original trace/span is lost - which can be important for book keeping and troubleshooting.

Give the facilities to link datasets back to spans when uploading:

px.Client().upload_dataset(
    dataframe=spans,
    input_keys=[],
    output_keys=[],
    span_id_key="context.span_id"
    dataset_name="real-estate",
)
@mikeldking mikeldking added enhancement New feature or request triage issues that need triage labels Aug 26, 2024
@github-project-automation github-project-automation bot moved this to 📘 Todo in phoenix Aug 26, 2024
@mikeldking mikeldking removed the triage issues that need triage label Aug 26, 2024
Copy link

dosubot bot commented Dec 25, 2024

Hi, @mikeldking. I'm Dosu, and I'm helping the Arize Phoenix team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • Enhancement proposal to retain links to original traces or spans upon dataset upload.
  • Aims to improve bookkeeping and troubleshooting by preserving span_id.
  • No further comments or activity since the issue was opened.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of the Arize Phoenix repository by commenting here.
  • If there is no further activity, the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed
Projects
Status: 📘 Todo
Development

No branches or pull requests

1 participant