Feature Have direct ASH access to counter information

get_counters(string, int, int) only returns a value if a counter is between those two integers. But what is the actual value of that counter? ASH scripts do not have a direct way of accessing that information. My FReq would request that information be exposed to ASH. A couple suggestions:

a no-argument version of get_counters that returns a record{string,int}[int] of the current active counters, including counters that are at 0
a get_counters(string) that returns the value of the named active counter or, if not active, -1