open-telemetry / open-telemetry/opentelemetry-python-contrib
Opentelemetry Psycopg2 version >2.7 | Failed to export batch code 404: 404 Page not found
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
Hello:
I am running AWS Lambda function that talks to Postgres database hosted on AWS. All I am doing is getting DB credentials from secret manager and then reading database version. Opentelemetry traces capture the interaction with secrets manager but do not capture the interaction with database.
Steps to reproduce
Create AWS Lambda to talk to database (Any read or write, it doesnt matter)
What is the expected behavior?
I expect to see trace that captures database call
What is the actual behavior?
DB trace is missing and instead I see the error in the logs. Failed to export batch code 404: 404 Page not found.
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
No repository files, tests, or entry points are named. Start by reproducing the AWS Lambda setup with psycopg2 and inspect the exporter configuration alongside the 404 logs; done means the database call produces a trace and the export error no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, postgresql, python
- Domain
- cloud, database, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100