# Observability for Dify with Opik

Learn how to connect Opik with Dify to monitor your applications' performance.

## Setup Instructions

Follow these simple steps to connect Dify with Opik:

1. Select the Dify app you want to monitor
2. Select **Monitoring** from the side menu
3. Click on **Tracing app performance**
4. Click on **Configure** for Opik
5. Enter your connection details based on your Opik version:

:::frame
<img src="../img/apps/opik-documentation/documentation/fern/img/tracing/dify_configuration.png" alt="">
:::

::::tabs
:::tab{title="Hosted Opik"}
Fill in these fields:

- **API Key**: Your Comet API Key
- **Project**: Your preferred project name (if left empty, it will be created automatically)
- **Workspace**: Your Comet Workspace name (must already exist)
- **URL**: Your Opik installation URL (make sure it ends with `/api/`)
:::

:::tab{title="Self-Hosted Opik"}
Fill in these fields:

- **API Key**: Leave this empty
- **Project**: Your preferred project name (if left empty, it will be created automatically)
- **Workspace**: Type `default`
- **URL**: Your Opik installation URL (make sure it ends with `/api/`)
:::
::::

## How to View Your Traces

After setup, you can view your application traces by:

1. Opening the **Monitoring** section from the side menu
2. Finding and clicking the **OPIK** button in the top-right corner
3. Selecting **View** to open your Opik project dashboard

:::frame
<img src="../img/apps/opik-documentation/documentation/fern/img/tracing/dify_view_project.png" alt="">
:::

## Related pages

- [.NET](./net-index.md)
- [Administration](./administration-index.md)
- [AI Coding Assistants](./ai-coding-assistants-index.md)
- [Changelog](../changelog.md)
- [Configuration](./configuration-index.md)
- [Contributing](./contributing-index.md)
- [Development](./development-index.md)
- [Evaluation](./evaluation-index.md)
- [Getting Started](./getting-started-index.md)
- [Guardrails](./guardrails-index.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.