Sorry I haven't been taking part in the discussion. Rhode Island celebrates VJ Day so I had the day off... Whatever.
Adding in reporting or views would be a good idea, but they were so easy to do after all the work around getting the data into a property bag, that it just didn't occur to me.
The goal of my process here was to gather data for long term reporting and trending, not as a monitor and response. That dictated the use of the Probe. That exposes the property bag object which is how you get data into OpsMgr for long term storage and management. The first time I created the rule and the scripts, I didn't get data because I had it set to run once a day. To verify it was working correctly, I initially created it with data collection for once every 5 minutes. Within a while, I think about 45 minutes, of creating the rule, I began to see data. It took a while for it to send it out to all the servers and then begin collecting.
The report I'm running currently is just a query using the RuleRowId to identify the appropriate rule. It'll be different in every system, so just query the vRule view to see which one is appropriate. I was also able to create view by selecting the rule name. It should be available after the data collection starts. If it isn't, there may be a problem with the script, or the Probe definition. I had a lot of trouble figuring out how to get the Probe definition right.
I'm sorry the article wasn't clear enough on these points. I was really hoping to help people who had been stuck like I was. It seems I may have just muddied the waters more.