anobre/openshift-resource-governance
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix: use UTC time for Prometheus queries to ensure correct time range calculation

Browse Source
This commit is contained in:
Anderson
2025-10-03 13:01:58 -03:00
parent 6ae9cbcef6
commit 61d7cda3d7
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
app/services/historical_analysis.py
View File

@@ -295,7 +295,7 @@ class HistoricalAnalysisService:
if time_range not in self.time_ranges:
time_range = '24h'
end_time = datetime.now()
end_time = datetime.utcnow()
start_time = end_time - timedelta(seconds=self.time_ranges[time_range])
try:
@@ -1353,7 +1353,7 @@ class HistoricalAnalysisService:
cpu_usage_query = f'rate(container_cpu_usage_seconds_total{{namespace="{namespace}", pod=~"{workload}.*"}}[5m])'
# Calculate time range
end_time = datetime.now()
end_time = datetime.utcnow()
start_time = end_time - timedelta(seconds=self.time_ranges.get(time_range, 86400))
# Query Prometheus
@@ -1404,7 +1404,7 @@ class HistoricalAnalysisService:
memory_usage_query = f'container_memory_working_set_bytes{{namespace="{namespace}", pod=~"{workload}.*", container!="", image!=""}}'
# Calculate time range
end_time = datetime.now()
end_time = datetime.utcnow()
start_time = end_time - timedelta(seconds=self.time_ranges.get(time_range, 86400))
# Query Prometheus