feat: google-vertexai-instrumentation#289
Conversation
|
@nirga Gemini Trace:
|
...es/opentelemetry-instrumentation-vertexai/opentelemetry/instrumentation/vertexai/__init__.py
Outdated
Show resolved
Hide resolved
...es/opentelemetry-instrumentation-vertexai/opentelemetry/instrumentation/vertexai/__init__.py
Outdated
Show resolved
Hide resolved
...es/opentelemetry-instrumentation-vertexai/opentelemetry/instrumentation/vertexai/__init__.py
Outdated
Show resolved
Hide resolved
...es/opentelemetry-instrumentation-vertexai/opentelemetry/instrumentation/vertexai/__init__.py
Outdated
Show resolved
Hide resolved
...es/opentelemetry-instrumentation-vertexai/opentelemetry/instrumentation/vertexai/__init__.py
Outdated
Show resolved
Hide resolved
|
@nirga Couldn't get model_name in the response and unable to find a way to correlate between model initialisation and the predict function call. Apart from the model_name other issues were resolved and pushed. |
There was a problem hiding this comment.
When trying to run poetry install I'm getting -
Warning: poetry.lock is not consistent with pyproject.toml. You may be getting improper dependencies. Run poetry lock [--no-update] to fix it.
Because traceloop-sdk depends on google-cloud-aiplatform (^1.38.1) which doesn't match any versions, version solving failed.
There was a problem hiding this comment.
When trying to run poetry install I'm getting -
Warning: poetry.lock is not consistent with pyproject.toml. You may be getting improper dependencies. Run poetry lock [--no-update] to fix it.
Because traceloop-sdk depends on google-cloud-aiplatform (^1.38.1) which doesn't match any versions, version solving failed.
...es/opentelemetry-instrumentation-vertexai/opentelemetry/instrumentation/vertexai/__init__.py
Outdated
Show resolved
Hide resolved
|
@nirga pushed the model_name solution |
afddbe0 to
773ca1d
Compare
94d7902 to
801b839
Compare
801b839 to
92ab5c4
Compare
Co-authored-by: Nir Gazit <nirga@users.noreply.github.com>





closes #249
/claim #249