Differences

This shows you the differences between two versions of the page.

--- historical_graphs [2021/08/05 14:19] – emozolyak
+++ historical_graphs [2023/03/23 09:56] (current) – [Log data size considerations] emozolyak
@@ Line 1: / Line 1: @@
-{{ :menu-icon-graphs.png?nolink&40|}}
+{{ network:menu-icon-graphs.png?nolink&40|}}
 ====== Historical graphs ======
@@ Line 11: / Line 11: @@
 This one is shown on a small time scale:
-{{::graph_example_pure_curve_steps.png?direct}}
+{{network:graph_example_pure_curve_steps.png?direct}}
 This one is shown on a large time scale:
-{{::graph_example_aerial_view_steps.png?direct}}
+{{network:graph_example_aerial_view_steps.png?direct}}
 Elements of the graph:
@@ Line 40: / Line 40: @@
 See the video:
-{{graph_navigate.gif?direct}}
+{{network:graph_navigate.gif?direct}}
 ==== Graph curve display features ====
@@ Line 48: / Line 48: @@
 In this example, the register's property was set to use data from log and save on every change. The sinus value was calcualted in a script executed each scan. Then system scan time was changed from 50 ms to 1 seconds. Becuase graph viewing area resoluon is 1 seconds, more data saved in database log for any given point when scan was 50 ms and that was highlighted with semitransparent zone along the curve.
-{{more_graph_data_in_one_sec.gif}}
+{{network:more_graph_data_in_one_sec.gif}}
 In the case when for a selected plot scale 1 minute or more will fit into 1 pixel of the screen, then the average values (5) of the register and the zone (4) of the range of values for estimating the distribution of the minimum and maximum peaks will be displayed on the graph. This averaging is drawn using cached data from the database, corresponding to the current scale of the view (in the database, averaging is stored for 1, 2, 5, 15 and 60 minutes). This method allows you to optimize the work with graphs when viewing large amounts of data on a different scale, while maintaining the speed of work.
@@ Line 56: / Line 56: @@
-==== Log data size considerations ====
-By **log** it is considered all the data, that accumulates on the device, such as:
-events log, event's registers log, meter's log, register's graph log, register's log and so on.
-The log depth can be adjusted in the Setup / Settings menu:
-{{::log_depth_scr_shot.png?direct}}
-Theoretically, the volume of the archive is limited only by the size of the flash card.
-It should be said that storing large amounts of data is not the target application of the device, although it allows it to do so. For the big amount of monitoring data, it is recommended to take care of data redundancy and use a special server which fetches log data via the API to the DB or the Level2 cloud server option.