doc update

docs/about.rst

@@ -58,7 +58,7 @@ The PA-nmon_light add-on is a minimal add-on designed to be installed on indexer
 Index time operations
 ---------------------
 
-The application operates index time operation, the PA-nmon_light add-on must be installed in indexers in order for the application to operate normally.
+The application operates index time operations, the PA-nmon_light add-on must be installed in indexers in order for the application to operate normally.
 
 If there are any Heavy forwarders acting as intermediate forwarders between indexers and Universal Forwarders, the TA-nmon add-on must deployed on the intermediate forwarders to achieve successfully index time extractions.
 
@@ -84,9 +84,10 @@ Summarization implementation
 
 Nmon for Splunk App intensively uses data model acceleration in almost every user interfaces, reports and dashboards.
 
-The application provides multiple data models that have the acceleration activated by default using "All time" as the time range limit for all data models managing performance and configuration data.
+**By default, data models are accelerated with the following settings:**
 
-The Nmon Processing data model is by default accelerated over last 3 months of data.
+- metrics related data models are accelerated over a period of 1 year
+- others data models are accelerated over the last 30 days
 
 Splunk Accelerated data models provide a great and efficient user experience.
 

docs/large_scale_deployment.rst

@@ -17,13 +17,16 @@ Data model acceleration
 Accelerated data models are massively used in the application, this implementation provides exceptional performances of searches, and a great user experience.
 However, data models have a cost in term of storage and system resources utilization for acceleration build and maintenance.
 
-By default, all data models are accelerated over the "All time" period, these settings are managed in the following configuration file:
+**By default, data models are accelerated with the following settings:**
+
+- metrics related data models are accelerated over a period of 1 year
+- others data models are accelerated over the last 30 days
 
 *nmon/default/datamodels.conf*
 
 ::
 
-    acceleration.earliest_time = 0
+    acceleration.earliest_time = -1y
 
 Restricting the acceleration period will helping reducing:
 
@@ -44,11 +47,11 @@ Finally, take care not to reduce too much the acceleration period, searches out
 
 You can easily customize the acceleration period by creating a local copy of the datamodels.conf under the "local" directory.
 
-Then, for each data model, ensure to set the required period, example with a 1 year period:
+Then, for each data model, ensure to set the required period, example with a 3 months period:
 
 ::
 
-    acceleration.earliest_time = 1y
+    acceleration.earliest_time = -3mon
 
 Acceleration setting of data models can also be managed directly in Splunk Web:
 
@@ -171,15 +174,3 @@ See: :ref:`manage_volume_per_server`
 The Nmon Performance technical add-ons generates csv flows of data, as such the volume of data to be generated is already really optimised and reduced to the maximum.
 
 However, you can choose to limit licence usage and storing costs by increasing the time between 2 performance collections, a common choice might be to increase this time to 2 or 3 minutes.
-
-
-
-
-
-
-
-
-
-
-
-