quality field means in pointvalues database table direct indicate one point is good or bad in a exact timestamt.
in ALL loggingType, if one timestamt no value,this can indicate it communication error.
in on_change type,we can use use "No Change" or "No Update" event detectors to indicate it communication error.

but when query pointvalue in api,chart,report ,just query data from pointvalue table,we don't join the event detectors to indicate one point is bad or good in a exact timestamt.

Yes, You can :
go to edit data point, go to second section of data point details - Property Template and click to edit templates , change what You want and save as new templates. In fact You can save many templates for more groups of data points

Clustering Mango for HA (high availability) and failover would be a great feature and very attractive to enterprise customers I think.

Personally, the greater value would be in having redundancy, rather than sharing load (as it seems Mango can scale very well itself anyway).

Some network monitoring systems (PRTG?) implement this in a way that means that one node/instance is doing the monitoring, and syncing data to a secondary instance, but if the primary goes down the secondary instantly detects this and takes over polling. When the primary comes back the data is resynced.

a typical error is one datapoint which in context var list be disabled, or be delete in other place,this datapoint var will occur ReferenceError: "p1" is not defined, and the next script will not execute.

I have tryed to use typeof p1 !=undefined or p1!=null to check first , but it seem like don't work.

And i have tested, it is base on cron time,so the cron need after the 0 clock.

sometimes, the datasources is interrupted because the nework problem or other reason, we can recover acquisition the data during the interrupted times.
now the datasource all save the value runtime(now time),so if we interrupted recover collect the data before,the timestamp is now but not the realy past time. Do have same case? and have some solutions.

hussam,

The beta release is ready here: https://github.com/infiniteautomation/ma-core-public/releases/tag/2.5.0-beta.1

Let us know of any issues you have by adding them here http://github.com/infiniteautomation/ma-core-public/issues

Thanks

hussam,

Thank you for letting us know about this. I will make sure this fix gets added to the next release. In the future feel free to add any potential bugs to our git Issue list here:

https://github.com/infiniteautomation/ma-core-public/issues

thanks you reply, And the important point is the pointvalue's timestamp, when we settable one point ,and set it's value , or update on Context when enters a new value,but the result pointvalue's timestamp is the now ,is not the original should be.

so,this can summarized execute one time pasted meta point,and update it's value into pasted timestamp .

sorry, I means when delete one point, but this point is used on another meta point's update context,so ,this meta point will be problem.

You can fork the repo on github https://github.com/infiniteautomation and then issue a pull request. You might also want to look at the video about the new pointDetails page in this post: http://infiniteautomation.com/forum/topic/1872/new-features-coming-soon

it is work now ,because the adblock plus 2.6 add-on conflict,when i disable the adblock plus 2.6,is ok.