crewAIInc / crewAIInc/crewAI

Integrate OpenTelemetry GenAI semantic conventions into CrewAI SDK

Open
#6,723 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request
Dominant language
Python
Stars
58.8k
Forks
8.5k
Avg merge
1d 15h
Merged PRs (30d)
109

Description

Feature Area

Core functionality

Is your feature request related to a an existing bug? Please link it here.

Hi CrewAI team,

We would like to collaborate & add Open Telemetry instrumentation GenAI instrumentation to this SDK.

Ongoing PR: https://github.com/open-telemetry/opentelemetry-python-genai/pull/308

This instrumentation will help to provide a vendor neutral way to observe AI applications and additionally it provides portability across observability vendors.

If this is something you would be interested in supporting, we would be happy to collaborate & contribute on the same.

Describe the solution you'd like

We are also exploring related work in the OpenTelemetry GenAI ecosystem and would be happy to collaborate on implementing this support.

Describe alternatives you've considered

No response

Additional context

No response

Willingness to Contribute

Yes, I'd be happy to submit a pull request

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 by reviewing the proposed OpenTelemetry GenAI instrumentation in the linked opentelemetry-python-genai PR and the CrewAI SDK's core functionality entry points. Clarify the supported semantic conventions, integration boundaries, and tests with the maintainers; done means CrewAI exposes the agreed vendor-neutral GenAI telemetry with coverage for the supported paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ai, observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.