From dd253dd179ebea4edd4c723005d062ff12476fcb Mon Sep 17 00:00:00 2001 From: Robin Date: Sat, 12 Oct 2024 13:45:24 -0700 Subject: [PATCH] Update emission/storage/decorations/stats_queries.py Co-authored-by: K. Shankari --- emission/storage/decorations/stats_queries.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/emission/storage/decorations/stats_queries.py b/emission/storage/decorations/stats_queries.py index d933d424f..9b5c4f215 100644 --- a/emission/storage/decorations/stats_queries.py +++ b/emission/storage/decorations/stats_queries.py @@ -48,7 +48,7 @@ def store_stats_entry(user_id, metadata_key, name, ts, reading): new_entry = ecwe.Entry.create_entry(user_id, metadata_key, data) return esta.TimeSeries.get_non_user_time_series().insert(new_entry) -def store_function_time(user_id: str, stage_string: str, ts: float, reading: float): +def store_dashboard_time(code_fragment_name: str, ts: float, reading: float): """ Stores statistics about execution times in dashboard code. Both of our current dashboards generate _aggregate_ metrics. I don't see that changing in the foreseeable future, since we don't really want to work at a per-user level in the python dashboards. So we don't pass in the user_id, only a string indicating the name of the step being instrumented, and the value.