From a43d078616c66956b220c9c7af941e60d229f087 Mon Sep 17 00:00:00 2001 From: DL6ER Date: Tue, 25 Feb 2025 05:47:37 +0100 Subject: [PATCH 1/2] Tweak wording of the history endpoint Signed-off-by: DL6ER --- src/api/docs/content/specs/history.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/api/docs/content/specs/history.yaml b/src/api/docs/content/specs/history.yaml index 3b52bc074..f97aab7f8 100644 --- a/src/api/docs/content/specs/history.yaml +++ b/src/api/docs/content/specs/history.yaml @@ -8,7 +8,7 @@ components: - Metrics operationId: "get_activity_metrics" description: | - Request data needed to generate the \"Query over last 24 hours\" graph. The sum of the values in the individual data arrays may be smaller than the total number of queries for the corresponding timestamp. The remaining queries are queries that do not fit into the shown categories (e.g. database busy, unknown status queries, etc.). + Request data needed to generate the total queries over time graph. The sum of the values in the individual data arrays may be smaller than the total number of queries for the corresponding timestamp. The remaining queries are queries that do not fit into the shown categories (e.g. database busy, unknown status queries, etc.). responses: '200': description: OK From ff9d81ce22b3225613bb9d9d1861dae910862ee2 Mon Sep 17 00:00:00 2001 From: DL6ER Date: Tue, 25 Feb 2025 05:47:58 +0100 Subject: [PATCH 2/2] Restart FTL to import more data in case of enlarging webserver.api.maxHistory. The graph would stay mostly empty (until it fills naturally over time), otherweise Signed-off-by: DL6ER --- src/config/config.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/config/config.c b/src/config/config.c index a2295a286..334e5f763 100644 --- a/src/config/config.c +++ b/src/config/config.c @@ -1161,6 +1161,7 @@ static void initConfig(struct config *conf) conf->webserver.api.maxHistory.k = "webserver.api.maxHistory"; conf->webserver.api.maxHistory.h = "How much history should be imported from the database and returned by the API [seconds]? (max 24*60*60 = 86400)"; conf->webserver.api.maxHistory.t = CONF_UINT; + conf->webserver.api.maxHistory.f = FLAG_RESTART_FTL; // Restart FTL to import more data in case of enlarging of this value conf->webserver.api.maxHistory.d.ui = MAXLOGAGE*3600; conf->webserver.api.maxHistory.c = validate_stub; // Only type-based checking