newrelic / newrelic/newrelic-python-agent
Time not attributed to boto3
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 210
- Forks
- 137
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 12
Description
New Relic profile incorrectly shows a few ms for the time to download/upload a file that takes several seconds
Description
boto3 was instrumented with the fix in #1178 but the time used by the download/upload of the file from/to S3 is attributed to the Python code that calls that rather than that function
Expected Behavior
Time would be correctly attributed to the boto3 code rather than the caller
Steps to Reproduce
- Run Python code that uses
boto3to download/upload a file from/to S3 - View profile information in New Relic
- Observe that time show for the
GETandHEADcalls to S3 are very small rather than the multiple seconds it takes
Your Environment
Python 3.12.7 with Debian Bookworm
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the boto3 instrumentation from #1178 and reproduce the issue with Python code that downloads or uploads an S3 file. Compare the profile attribution for the S3 GET and HEAD calls with the caller; done means the several seconds of transfer time are attributed to boto3 rather than the calling Python code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100