Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace 'session' with 'trace' in Documentation and Examples #851

Open
12 tasks
devin-ai-integration bot opened this issue Mar 15, 2025 · 0 comments
Open
12 tasks

Replace 'session' with 'trace' in Documentation and Examples #851

devin-ai-integration bot opened this issue Mar 15, 2025 · 0 comments

Comments

@devin-ai-integration
Copy link
Contributor

Replace "session" with "trace" in Documentation and Comments

Description

As part of our transition to OpenTelemetry standards, we need to replace the notion of "sessions" with "traces" in our documentation and code comments. This issue focuses on updating documentation files, code comments, and examples in both repositories.

Current State

  • AgentOps.Next has 17 markdown files with session references
  • AgentOps has approximately 50 documentation files with session references
  • Code comments throughout both repositories use session terminology
  • Example code and notebooks use session terminology

Required Changes

AgentOps.Next Repository

  • Update markdown documentation files
  • Update API documentation to reflect trace terminology
  • Update code comments in API routes and handlers
  • Update code comments in dashboard components

AgentOps Repository

  • Update concept documentation:
    • /docs/v1/concepts/ session-related documentation → trace-related documentation
  • Update usage documentation:
    • /docs/v1/usage/ session examples → trace examples
  • Update example code and notebooks:
    • /examples/ session usage → trace usage
  • Update OpenTelemetry integration documentation
  • Update code comments throughout the codebase

Implementation Considerations

  • Ensure consistent terminology throughout documentation
  • Update diagrams and visual aids
  • Provide migration guides for users transitioning from sessions to traces
  • Coordinate with API and UI changes

Acceptance Criteria

  • All documentation uses "trace" terminology
  • Code comments consistently use trace terminology
  • Example code demonstrates trace-based usage
  • Migration guides are provided for users
  • Documentation accurately reflects the updated API and UI

Related Issues

  • API endpoint changes for session to trace transition
  • Database schema changes for session to trace transition
  • UI component updates for session to trace transition
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants