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

[Python] Evaluate Product Experience #12

Open
2 of 10 tasks
smeubank opened this issue Nov 28, 2022 · 2 comments
Open
2 of 10 tasks

[Python] Evaluate Product Experience #12

smeubank opened this issue Nov 28, 2022 · 2 comments
Assignees

Comments

@smeubank
Copy link
Member

smeubank commented Nov 28, 2022

Description

We should be prepared to address the quality of the Sentry Product Experience for all users considering our new Sentry + OTEL approach

What Major platforms can we ensure it works for?

  • Python SDK
    • Django
    • Flask
    • FastAPI
    • Other non-web framework related?

Product Features

  • Error Tracking
    • What do users have to do?
    • What works?
      • Issues
        • 'POST /test/12344?test=true'
          • returns an error - should be reflected
        • Stack trace and code link
        • Bread crumbs
      • Related transactions
      • Trace view
      • Performance Issues
        • New and rely on standardized txns and spans
    • What doesn’t work, or doesn’t work quite the same?
  • Performance Monitoring
    • What do they have to do?
    • What works?
      • Distributed tracing
      • Transactions and Spans
        - Naming, descriptions, etc
        - Operation: http.server
        - [ ] parameterized transactions
        • GET /?test=true
        • 'POST /test/12344?test=true'
          - [ ] http.method
          - [ ] related issues
          - Operation: queue.task.____
          - Operation: integration.http
          - Operation: db
      • Vitals
        • User Misery
        • [] Backend
    • What doesn’t work or doesn’t work the same?
  • Release Management
    • Adoption, Crash related features
    • Source Maps: N/A
  • Discover & Dashboards
  • Ecosystem & Workflow
    • consider product integration dependent upon incoming data
    • alerts for example
  • Profiling
    • statement on if it CAN work
  • Replays
    • statement on if it CAN work
@smeubank smeubank added the enhancement New feature or request label Nov 28, 2022
@smeubank
Copy link
Member Author

Issue to be treated as a check list

Outcomes

  • Do we need to add more documentation?
  • Do we need to communicate this to other product teams? (create issues)
  • Do we need to consider upstream contribution? (only create issues for now)
  • Do we need to improve the span transformation and/or trace propagation? (create issues)

@smeubank
Copy link
Member Author

  • integration tests for each platform
    • clarify the tests to run on each SDK
  • how to convert this into automated functional testing
    • apply per repo
    • apply to hipster shop

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants