DRY out instrumentation

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
observability-sre

Research direction

Start by locating the repeated instrumentation code that checks whether functions exist and applies decorators, then compare how the library integrations duplicate those steps. Done means the shared instrumentation approach reduces boilerplate for adding a new library without changing existing instrumentation behavior; add or update tests for the affected integrations.

Written by the indexing model from the issue text.

Description

There's a lot of boilerplate at the moment around instrumenting a function in a library - checking if the function is there, adding the decorator around it, etc. It would be nice to remove some of that duplication to reduce the effort to instrument a new library.

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.