getsentry / getsentry/sentry-python

Decide what to do with `@ai_track` decorator.

Open
#4,854 1 comment 0 reactions 0 assignees View on GitHub
AI Insights Python Task
Dominant language
Python
Stars
2.2k
Forks
669
Avg merge
1d 1h
Merged PRs (30d)
213

Description

We have a decorator [@ai_track](https://github.com/getsentry/sentry-python/blob/master/sentry_sdk/ai/monitoring.py#L30) which creates spans with an `op` either `ai.run` or `ai.pipeline`.

With the new AI insights module and agentic coding the concept of a AI pipeline is maybe not as important anymore?

We need to make a decision if we want to deprecated `@ai_track` or if we want to change it to make it work with the AI insights in Sentry.

The only documentation of the decorator I could find is this blog post: https://blog.sentry.io/ai-application-insights-with-sentry-llm-monitoring/

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.