move tracer to skyvern init

[wintonzheng]

🚀	This description was created by Ellipsis for commit 5a1b01f

Summary:

Moved ddtrace tracer configuration to skyvern/__init__.py for centralized initialization.

Key points:

• Moved ddtrace tracer configuration from skyvern/forge/app.py to skyvern/__init__.py.
• Ensures tracer is configured during skyvern module initialization.
• Removed redundant tracer configuration from skyvern/forge/app.py.
• Affects skyvern/__init__.py and skyvern/forge/app.py.

---

Generated with ❤️ by ellipsis.dev

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 5a1b01f in 31 seconds

More details

• Looked at 47 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. skyvern/__init__.py:6

• Draft comment:
  Moving the tracer configuration to __init__.py is a good practice for centralizing setup logic and ensuring it's executed before other imports. This helps in maintaining cleaner code and avoiding potential issues with the order of imports.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The PR moves the tracer configuration from skyvern/forge/app.py to skyvern/__init__.py. This centralizes the tracer setup, which is a common practice for better maintainability and to ensure that the tracer is configured before any other imports that might use it. This change seems appropriate as it avoids potential issues where the tracer might be used before being configured if other modules are loaded before app.py. The use of FilterRequestsOnUrl to filter out specific URLs (like heartbeat checks) from tracing is also a good practice to reduce unnecessary logging and overhead.

Workflow ID: wflow_SvvWaQhy0Il5ZfSh

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.