Prototype @instrument with OTEL

[sfc-gh-gtokernliang]

Description

Create an @Instrument decorator that emits the OTEL spans to the created Event table

Other details good to know for developers

N/A

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to
  not work as expected)
• New Tests
• This change includes re-generated golden test results
• This change requires a documentation update

---

Important

Adds @instrument decorator for OpenTelemetry tracing, enhances Snowflake support in SQLAlchemy, and includes tests for new functionality.

• New Feature:
  • Adds @instrument decorator in instrument.py for OpenTelemetry tracing, emitting OTEL spans.
  • Validates attributes, including TRULENS_SELECTOR_NAME from semantic.py.
  • Handles exceptions by setting span status to STATUS_CODE_ERROR.
• Database:
  • Adds patch_insert function in sqlalchemy.py to support Snowflake OBJECT in SQLAlchemy ORM.
  • Adds get_db_dialect() method in SQLAlchemyDB class in sqlalchemy.py.
• Export:
  • Updates export() in exporter.py to correctly handle parent_id for spans.
  • Adds event_id to _construct_event() in exporter.py.
• Tests:
  • Adds test_otel_instrument.py to test @instrument decorator functionality.
  • Includes golden file test_otel_instrument__test_deterministic_app_id.csv for expected results.
  • Updates WithJSONTestCase in test.py to handle .csv and .parquet formats.

^{This description was created by for a1c461c. It will automatically update as commits are pushed.}

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[sfc-gh-dkurokawa]

also should validate that span types are a string too. Unless you plan on folding it into the TODO on L35.

[sfc-gh-gtokernliang]

yeah I was thinking of folding it into the TODO - basically:

1. If the span type is provided, it must match one of the provided span types in the semcov package.
2. Otherwise it's unknown.

[sfc-gh-dkurokawa]

this won't prepend any namespaces but maybe it's just okay to get the user to say the full attribute name (i.e. with the scopes) themselves. If that's your idea, I'm good with that (so long as later when we validate spans with a given span type follow the semantic convention of that span type and throw an error I'm good).

[sfc-gh-gtokernliang]

updated to prepend namespace

[ellipsis-dev]

Add assertions to verify the expected behavior instead of just printing recording. This will ensure the test checks if spans are correctly emitted and stored.