Hi,
See below,
This works fine when the values of Counter64 are running at the right rate and are always available. It seems that sometimes a value is missed which results in a large delta in the graph.
Let me double check this here, a missed value should not result in this kind of spike. It maybe that a missed Counter64 value is being interpreted as zero. That would be a bug with Unbrowse.
We dont have much plans for the poller, the main use case is a simple and responsive graphing tool to aid diagnostic. We will certainly accomodate requests for improvement. What do you have in mind for "conditional graphing" ?