Merge pull request #586 from Qovery/chore/update_obs_history_service_logs

Update service logs history for observability

Author: jul-dan

website/docs/using-qovery/deployment/logs.md

@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2025-10-08"
+last_modified_on: "2025-10-15"
 title: Logs
 description: "Learn how to access the logs of your environment and services"
 ---
@@ -113,7 +113,7 @@ Past application logs are preserved on your cluster via [Loki](https://grafana.c
 
 | Feature | With Observability Package | Without Observability Package |
 |---------|---------------------------|-------------------------------|
-| **History** | 12 weeks of complete log history | 3 days maximum |
+| **History** | 12 weeks of complete log history | 24 hours maximum |
 | **Volume** | Unlimited lines | Latest 1000 lines per service only |
 | **Capabilities** | Advanced filtering and correlation with metrics | Real-time logs only - no historical search |
 

website/docs/using-qovery/deployment/logs.md.erb

@@ -104,7 +104,7 @@ Past application logs are preserved on your cluster via [Loki](https://grafana.c
 
 | Feature | With Observability Package | Without Observability Package |
 |---------|---------------------------|-------------------------------|
-| **History** | 12 weeks of complete log history | 3 days maximum |
+| **History** | 12 weeks of complete log history | 24 hours maximum |
 | **Volume** | Unlimited lines | Latest 1000 lines per service only |
 | **Capabilities** | Advanced filtering and correlation with metrics | Real-time logs only - no historical search |
 

website/docs/using-qovery/observability/logs.md

@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2025-10-08"
+last_modified_on: "2025-10-15"
 title: Services logs
 description: "Services logs"
 sidebar_label: Services logs
@@ -23,7 +23,7 @@ In addition to real-time monitoring, Qovery observability includes **logs** to h
 
 Every service in Qovery has its own log stream, collected and stored via **Loki + Promtail**. (See the [Logs Section][docs.using-qovery.deployment.logs] to know more)
 
-- **Full historical access**: Complete log history with 12 weeks retention when observability is enabled, or 3 days without it
+- **Full historical access**: Complete log history with 12 weeks retention when observability is enabled, or 24 hours without it
 - Logs are enriched with **Qovery-specific labels** such as service ID and environment ID for easier filtering  
 - Error-level logs are automatically detected and counted, making it easy to correlate metrics with log spikes  
 

website/docs/using-qovery/observability/logs.md.erb

@@ -14,7 +14,7 @@ In addition to real-time monitoring, Qovery observability includes **logs** to h
 
 Every service in Qovery has its own log stream, collected and stored via **Loki + Promtail**. (See the [Logs Section][docs.using-qovery.deployment.logs] to know more)
 
-- **Full historical access**: Complete log history with 12 weeks retention when observability is enabled, or 3 days without it
+- **Full historical access**: Complete log history with 12 weeks retention when observability is enabled, or 24 hours without it
 - Logs are enriched with **Qovery-specific labels** such as service ID and environment ID for easier filtering  
 - Error-level logs are automatically detected and counted, making it easy to correlate metrics with log spikes