From 31d86997f54979ed995eb368ff969d71138e1db5 Mon Sep 17 00:00:00 2001 From: Pierre-Yves Chibon Date: Wed, 17 Feb 2021 09:59:51 +0100 Subject: [PATCH] Add a doc about the DEFAULT_QUERY_DELTA setting of datagrepper Signed-off-by: Pierre-Yves Chibon --- docs/datanommer_datagrepper/default_delta.rst | 18 ++++++++++++++++++ docs/datanommer_datagrepper/index.rst | 1 + 2 files changed, 19 insertions(+) create mode 100644 docs/datanommer_datagrepper/default_delta.rst diff --git a/docs/datanommer_datagrepper/default_delta.rst b/docs/datanommer_datagrepper/default_delta.rst new file mode 100644 index 0000000..256a94a --- /dev/null +++ b/docs/datanommer_datagrepper/default_delta.rst @@ -0,0 +1,18 @@ +Default delta +============= + +Checking the current status of datagrepper, we realized that not specifying a +`delta` value in the URL led to timeouts while specifying one, makes datagrepper +return properly. + +Investigating the configuration options of datagrepper, we found out that +there is a `DEFAULT_QUERY_DELTA` configuration key that allows to specify a +default delta value when one is not specified. + +Just setting that configuration key to ``60*60*24*3`` (ie: 3 days) improves the +datagrepper performances quite a bit (as in queries actually return instead of +timing out). + + +That configuration change, does break the API a little bit as with it, it will +limit the messages returned to the last 3 days. diff --git a/docs/datanommer_datagrepper/index.rst b/docs/datanommer_datagrepper/index.rst index 0d879a6..75f893a 100644 --- a/docs/datanommer_datagrepper/index.rst +++ b/docs/datanommer_datagrepper/index.rst @@ -28,6 +28,7 @@ Here is the list of ideas/things we looked at: .. toctree:: :maxdepth: 1 + default_delta pg_stat_statements pg_partitioning pg_timescaledb