traceloop / traceloop/openllmetry

๐Ÿ› Bug Report: Haystack example does not produce prompts in the spans

Open
#1,169 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
7.4k
Forks
1.1k
Avg merge
8d 14h
Merged PRs (30d)
2

Description

Which component is this bug for?

Haystack Instrumentation

๐Ÿ“œ Description

Hi, I am running the haystack sample. Looks like traces does not have information about the components of the pipeline and the input and output to the pipeline.
Do you have plans to add this? Has there been any discussion about this that I can read?
Thanks.

๐Ÿ‘Ÿ Reproduction steps

Run the code in haystack_app.py.

The root span produced does not have the input and output prompts

๐Ÿ‘ Expected behavior

The output spans should have the input and output prompts in the root span.

๐Ÿ‘Ž Actual Behavior with Screenshots

The attributes field should have the following fields

"traceloop.entity.input"
"traceloop.entity.output"

๐Ÿค– Python Version

No response

๐Ÿ“ƒ Provide any additional context for the Bug.

No response

๐Ÿ‘€ Have you spent some time to check if this bug has been raised before?
  • I checked and didn't find similar issue
Are you willing to submit PR?

None

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up โ€” it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the Haystack sample in packages/sample-app/sample_app/haystack_app.py and inspect the root span it produces. Trace the Haystack instrumentation path to determine why pipeline input and output are absent; done means the root span includes traceloop.entity.input and traceloop.entity.output attributes.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.