ProfessorI can't believe I am responding to a 4.5 year old topic, but aggregated data handling is sorely needed. We have an example currently where we care about total ISDN B-channel usage across two or more voice gateways. The only option we can come up with is to use the API within a custom datasource, which is a PITA without library support (topic of another FR I filed some time back). Thanks to @Steve Francis we at least have some sample code to get API data collected, but...wow. It should be possible to do this more directly within datasource definitions. Alternatively, allow people to set alerts on widgets, which do allow aggregation of data like this.
