In a MySQL system I noticed that the avg trend table will have a number of records added for a period of time after the element is Paused. These entries will have timestamps for the next couple of 5Min intervals past the time the element was paused. After about 20 min or so it appears to stop adding records. Below are the contents of the table about 20 min after the element was paused.
Can anyone explain why this is and how the logic works when element are paused or go into timeout?
Thanks
Hey Jeff,
If this is the local database (not offload), additional points being added after element pause is likely due to how average points are generated. When you pause an element, average trend values will still be generated if the average value changes. Here is an example:
- 12:02 – element paused
- 12:05 – average value calculated for 12:00-12:05
- 12:10 – different average value calculated for 12:05-12:10
You can see this in the CSV.
Once the average values stop varying, it should stop adding the records.
Regards,
Hi Jeff – I’m not sure, so this might have to be confirmed, but I thought also that DataMiner is actually buffering readings from devices, and then bulk inserting those in the actual database, because this is more efficient and less stressful for the database. So, I’m wondering if this might also be something to take into account.
Thank you for your response Ben.
Jeremiah,
Thanks for your response and info. I figured this was the behavior.