---
title: Application tracing
url: https://www.tines.com/docs/self-hosted/monitoring-tines/application-tracing/
updated: 2026-03-27T13:58:55+00:00
---

*[tines.com](https://www.tines.com/llms.txt) › [Docs](https://www.tines.com/llms.txt) › [Self-Hosted](https://www.tines.com/llm/docs/self-hosted.md) › [Monitoring Tines](https://www.tines.com/llm/docs/self-hosted/monitoring-tines.md)*

# Application tracing

*[View on tines.com](https://www.tines.com/docs/self-hosted/monitoring-tines/application-tracing/)*

## Tracing 

For deeper application-level observability, we recommend enabling **OpenTelemetry (OTEL) tracing**. This provides visibility into web requests, background job execution, database queries, external API calls, and more — going beyond infrastructure metrics to help you diagnose performance bottlenecks.

At a minimum, set `OTEL_ENABLED=true` on your `tines-app` and `tines-sidekiq` containers and point `OTEL_EXPORTER_OTLP_ENDPOINT` at your collector. Enabling `OTEL_AUTO_INSTRUMENTATION=true` captures a broad set of spans with no additional code changes.

See [OpenTelemetry Traces configuration](https://www.tines.com/docs/self-hosted/configuring-tines/opentelemetry-traces/) for full setup details and collector filter recommendations.