> ## Documentation Index
> Fetch the complete documentation index at: https://docs.langchain.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure SmithDB observability

> Scrape SmithDB application metrics and export logs and traces to your existing observability stack.

SmithDB components expose application metrics and can export logs and traces to your existing observability stack. Set this up after you deploy SmithDB services and before you tune capacity or migrate historical data. It provides the signals to validate those changes and investigate failures.

## Metrics

Each SmithDB component exposes application metrics at the fixed `/metrics` path on its HTTP port. Configure your monitoring stack to discover the pods by adding scrape annotations to each component:

<Accordion title="Sample Prometheus configuration">
  ```yaml theme={"theme":{"light":"catppuccin-latte","dark":"catppuccin-mocha"}}
  smithdb:
    query:
      deployment:
        annotations:
          prometheus.io/scrape: "true"
          prometheus.io/path: "/metrics"
          prometheus.io/port: "8060"
    ingestion:
      deployment:
        annotations:
          prometheus.io/scrape: "true"
          prometheus.io/path: "/metrics"
          prometheus.io/port: "8050"
    compaction:
      deployment:
        annotations:
          prometheus.io/scrape: "true"
          prometheus.io/path: "/metrics"
          prometheus.io/port: "8070"
    compactionWorker:
      deployment:
        annotations:
          prometheus.io/scrape: "true"
          prometheus.io/path: "/metrics"
          prometheus.io/port: "9000"
    clusterManager:
      deployment:
        annotations:
          prometheus.io/scrape: "true"
          prometheus.io/path: "/metrics"
          prometheus.io/port: "8090"
  ```
</Accordion>

These are Prometheus-style annotations. Providers with their own discovery format, such as Datadog, need that format applied to the same ports and path. Monitor the PostgreSQL metastore, Kubernetes nodes, and cloud services with your existing infrastructure monitoring.

For which metrics to watch and how to read them, see [SmithDB metrics reference](/langsmith/self-host-smithdb-metrics).

## Logs and traces

SmithDB uses the chart-level OpenTelemetry tracing configuration described in [Export LangSmith telemetry to your observability backend](/langsmith/export-backend), with one difference: SmithDB exports over OTLP gRPC only. Set `config.observability.tracing.exporter` to `grpc`. With `http`, SmithDB export stays disabled and SmithDB logs remain console-only. The chart adds SmithDB pod and container names as OpenTelemetry resource attributes automatically.

To customize SmithDB log filtering, set `RUST_LOG` for all SmithDB workloads through `smithdb.commonEnv`:

```yaml theme={"theme":{"light":"catppuccin-latte","dark":"catppuccin-mocha"}}
smithdb:
  commonEnv:
    - name: RUST_LOG
      value: "warn,smithdb_query=debug,vortex=warn"
```

Confirm the collector is reachable from the LangSmith namespace, apply the chart, then confirm telemetry arrives. To set up or tune a collector, see [Configure your collector for LangSmith telemetry](/langsmith/langsmith-collector).

***

<div className="source-links">
  <Callout icon="terminal-2">
    [Connect these docs](/use-these-docs) to your agent of choice via MCP for real-time answers.
  </Callout>

  <Callout icon="edit">
    [Edit this page on GitHub](https://github.com/langchain-ai/docs/edit/main/src/langsmith/self-host-smithdb-observability.mdx) or [file an issue](https://github.com/langchain-ai/docs/issues/new/choose).
  </Callout>
</div>