open-telemetry / open-telemetry/opentelemetry-python-contrib

Add instrumentation for discord.py library

Open
#4,492 6 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request
Dominant language
Python
Stars
1.1k
Forks
1.1k
Avg merge
4d 15h
Merged PRs (30d)
16

Description

What problem do you want to solve?

The discord.py library provides a framework for writing Discord bots with helpers for commands and listeners. There is nothing providing tracing support for this at the moment, limiting the out-of-the-box instrumentation experience to the underlying aiohttp library.

Describe the solution you'd like

discord.py has events (on_message, on_member_join, ...) and commands. Having traces on these events would provide meaningful data, showing what happens when a user interacts with the bot.

Describe alternatives you've considered

I've started drafting my own implementation for my bot over here, but I realized I'm not the only one who could benefit from this.

Additional Context

No response

Would you like to implement a fix?

Yes

Tip

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

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 with the discord.py event reference and commands documentation, then review the linked BallsDex-DiscordBot draft for an existing implementation direction. Compare that approach with this repository’s instrumentation conventions. Done means traces are available for meaningful discord.py events and commands, with behavior verified for representative bot interactions.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.