I've been working with some developers on the following information:
Many products treat counters as transient objects to be used in occasional interactive troubleshooting. This conflicts with our PI Interface for Performance Monitoring (PIPerfMon) which was designed with the expectation that the counter name is persistent. If you intend to stick with PIPerfMon tags, a tag modification routine is likely the best because only solution.
We do not have control over the StreamInsight server and have very limited view into the process(es). You are using the AF SDK to stream data into and out of StreamInsight. At that level you have about as much control as anyone can have.
Event Flow Debugger is for debugging and is taxing on performance. So it might help troubleshooting performance issues.
The Interface Team is considering rewriting the PI Interface for Performance Monitoring in the relatively near future. Your use case looks like an “interesting” test case.
We are running a number of queries that collectively use the AF SDK but we want to monitor data volume/availability across all queries, not all the data for the query comes from a PI stream. The idea is to predict degrades in query performance across 100's of installations. Perfmon was going to be a quick win until this issue.
Will let you know where we end up.
New PI Interface for Perfmon is interesting, I saw it recently had an update for the first time in years.