Skip to content

Commit 5a70638

Browse files
committed
fix: ai slop
1 parent 5d072ae commit 5a70638

1 file changed

Lines changed: 0 additions & 34 deletions

File tree

docs/getting-started/advanced-topics/observability.md

Lines changed: 0 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -64,40 +64,6 @@ The `utils/telemetry/metrics.py` module exports the following metrics:
6464

6565
Metrics are pushed to the Collector (OTLP) every 10 seconds and can be visualized in Prometheus → Grafana.
6666

67-
## 📈 Grafana Dashboard Setup
68-
69-
The example LGTM image has pre-configured data source UIDs: `tempo`, `prometheus`, and `loki`.
70-
71-
### Importing Dashboard Configuration
72-
73-
1. **Dashboards → Import → Upload JSON**
74-
2. Paste the provided JSON configuration (`docs/dashboards/ollama.json`) → Import
75-
3. An "Ollama" dashboard will be created in the `Open WebUI` folder
76-
77-
![Dashboard Import Configuration](/images/tutorials/otel/dashboards-config-import.png)
78-
79-
For persistent dashboard provisioning, mount the provisioning directories:
80-
81-
```yaml
82-
grafana:
83-
volumes:
84-
- ./grafana/dashboards:/etc/grafana/dashboards:ro
85-
- ./grafana/provisioning/dashboards:/etc/grafana/provisioning/dashboards:ro
86-
```
87-
88-
### Exploring Metrics with Prometheus
89-
90-
You can explore and query metrics directly using Grafana's Explore feature:
91-
92-
![Explore Prometheus Queries](/images/tutorials/otel/explore-prometheus.png)
93-
94-
This allows you to:
95-
- Run custom PromQL queries to analyze API call patterns
96-
- Monitor request rates, error rates, and response times
97-
- Create custom visualizations for specific metrics
98-
99-
100-
10167
## 🔧 Custom Collector Setup
10268

10369
If you're running your own OpenTelemetry Collector instead of the provided `docker-compose.otel.yaml`:

0 commit comments

Comments
 (0)