Good Morning,
We want to know it iss possible to increase timeframe records of the dataavg table, on the configuration of the dataminer - central database we only had three options:
Offload: All timefrane records (5 minutes, 60 minutes)
Only short timeframe records (5 minutes)
Only long timeframe records (60 minutes)
For example if we can execute the offload of the table every 15 mins, 30 mins or the time that we want.
Regards
Hey Javier,
The dropdown you mentioned relates to the type of trendpoint you want to offload. It has no relation or impact on the interval when the data will be actually offloaded.
To set the interval to i.e. 15 minutes, simply fill in 15 in the "Set the offload interval (in minutes) to"-option. See: Configuring the offload rate
Do note this applies to the whole dataset, it is not possible to configure this on a table by table basis.
If however you want to alter the window used for the average calculation, for example use 15 minutes worth of trending to calculate an average trendpoint, then you need to alter the trendwindow property for the trending module. This is described in the MaintenanceSettings.xml
Good Morning Bent,
Thanks for the information, so in our configuration the data will be oflload on this way:
Set the offload interval (in minutes) to 5 mins (Image 1), and on the table data the data will be uploaded every 30 mins and on table dataavg the data will be uploaded every 60 mins (Image 2),
On the table data every 30 mins will updated the information for example of the 12:55 pm, 01:00 pm, 01:05 pm etc, is that the function of the configuration? The same case for dataavg just for 60 mins?
Regards
What will be the funcionality of this options (on yellow).
Good Afternoon Bent,
So, if we had set the offload interval (in minutes) to 5 (Like the image):
The offload of the tables data and dataavg will be on 5 minutes?
Which is the funcionality of the Tren data enable options with the time?
Regards
Hi Javier,
The offload interval (5 minutes) is when the data is uploaded to the database.
The time options under trend data is when a new dataset will be generated and queued for pushing to the central DB.
So in this example: the following timeline should happen
12:55:00- short avg window generated and is uploaded to the central DB. (no trend data queued, no Long window queued)
13:00:00-long and short avg window generated and queued and data is uploaded to the DB. (no trend data queued)
13:05:00-short avg windows generated and queued, queued data is uploaded to the DB. (no trend data queued, no long avg queued)
13:10:00-short avg windows generated and queued, queued data is uploaded to the DB. (no trend data queued, no long avg queued)
13:15:00-short avg windows generated and queued, queued data is uploaded to the DB. (no trend data queued, no long avg queued)
13:20:00-short avg windows generated and queued, trend data generated and queued, queued data is uploaded to the DB. (no long avg queued)
Hey Javier,
The Offload Once every minutes. Decides how often these values are generated. It is meant to be able to collect the data without being tied to when the data is actually pushed to the central DataBase. As an example you set the general offload time to 5 minutes and the trend data offload to 7 minutes (starting at 12:00:00). then the following cycle will happen
12:05- Offload timer fires, no trend data has been generated so it is not uploaded
12:07-trend data has been generated but not uploaded
12:10-Data is uploaded (included the 12:07 trend data)
12:14-new set of trend data is generate but not uploaded.
12:15-Data is uploaded to the db
….
The second setting you highlighted relates to average trending. You can choose there which average trendpoints you want.
(short 5-minutes) are gnerated by the system every 5 minutes
(long 60-minutes) are generated once every hour.
Just like the previous example this is when the data is generated, not when it is uploaded. So to reuse the example, only offloading the long timeframes, with an offload rate of 5 minutes will create the following cycle
12:00:00-trend data is generated and uploaded
12:05:00-Data is pushed to the central DB but no new avg trending is present
12:10:00-Data is pushed to the central DB but no new avg trending is present
12:15:00-Data is pushed to the central DB but no new avg trending is present
….
13:00:00-trend data is generated and uploaded
I hope this clarifies the questions a bit