I know about PI ping which used to ping different servers in the PI architecture. But PI PING itself is enough to tell network slowness or do we need to monitor additional tags?
Other possible counters to monitor might be those under Network Interface. You can monitor these with the PI Interface for Performance Monitor.
I would suggest you to check application performance counters for each component you are deploying. CPU,Memory play important role in application if it needs high resources. It is better to understand whether delay is caused by network or application.
Hi Lal Babu,
Do we have any performance counters to monitor "Tunnler" for OPC DA interfaces?
If you planning to monitor OPC DA interfaces then would suggest you to use IO Rate, HeartBeat and Device Status to know the interface status. Device status gives an info about your connectivity from DA interface to DA server. If you are using UniInt failover then request you to use UFO counter which includes IO Rate, HeartBeat and Device Status. You can also use Interface Point Count counter to check that status when loading or restarting interface.
Eugene Lee shows a good few counters to monitor.
I would challenge you to define "slow" in your circumstance.
You need to consider if it is a LAN or WAN slowness, network infrastructure between the PI System and Data Collector Nodes and Clients etc.
Bandwidth saturation, network connection types (e.g. VSAT) and so on. Might not even be the network causing the perceived slowness.
If you can identify where the bottleneck is it is easier to pinpoint areas to monitor.
Retrieving data ...