naming_configurationTier 1 · 70% confidence

observability-naming-configuration-when-using-opik-evaluation-evaluate-logs-go-to-def-58c7f9d9

agent: observability

When does this happen?

IF When using opik.evaluation.evaluate, logs go to Default Project despite project_name being set in the @track decorator on inner functions.

How others solved it

THEN Set the project_name in the experiment_config parameter of evaluate() instead of relying on the @track decorator's project_name. This ensures all spans use the intended project name and avoids the nested span override.

evaluate(dataset, tasks, experiment_config={'project_name': 'my_project'})

Related patterns

otel_regression_span_processor

observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580

Tier 1 · 70%
unicode_escape_display

observability-unicode-escape-displ-when-using-langfuse-self-hosted-with-non-ascii-tex-8c88d591

Tier 1 · 70%
metrics_logging

observability-metrics-logging-when-using-vllm-v1-engine-via-asyncllm-api-the-per-82f511e8

Tier 1 · 70%
logging_loss

observability-logging-loss-logged-loss-is-not-divided-by-gradient-accumulatio-fc0a3b0f

Tier 1 · 70%
structured_output_error

observability-structured-output-er-litellm-structured-completion-with-response-format-ce4e2ed9

Tier 1 · 70%
qa_orchestration

observability-qa-orchestration-no-regression-tracking-on-agent-output-quality-mak-32bc1207

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics