Failed instrument messages

Open
#525 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the instrumentation failure messages in the Python agent and inspect how those failures are currently logged. Update the relevant messages so the INFO output explains the missing attribute and likely unsupported library version, while the DEBUG output retains the stack trace. Done means failed instrumentation produces both levels of logging as described.

Written by the indexing model from the issue text.

Description

As suggested by @cschneid :

  • Log friendly message with INFO, like "Failed to find attribute X, probably due to an unsupported version of library Y"
  • Log stack trace on DEBUG level.
Dominant language
Python
Stars
77
Forks
19
Avg merge
1d 9h
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

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.

More from scoutapp/scout_apm_python

All issues in scoutapp/scout_apm_python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.