Please stop monitoring deprecated products and subsystems, especially when the successor is also monitored by NOC. This will help steer customers towards using the successor by removing some of their reason to continue using the deprecated products and subsystems.

PI Agent currently uses TLS 1.0 to communicate with other PI Agent services in the crosslink configuration. TLS 1.0 is known to be insecure. Please update PI Agent so that it uses TLS 1.2 or TLS 1.3.

If you run the PI Diagnostics install kit without PI SDK already installed, the installation will fail with an error message stating that PI SDK is required. Other install kits include a copy of programs that they require. Please include PI SDK in the PI Diagnostics install kit.

In the longer term, PI Diagnostics should be rewritten to use PI AF SDK or be replaced with a product that does not use PI SDK. A modern PI server may need PI SDK only for PI Diagnostics.

If multiple recipients get the original NOC email alert, then if a site contact is assigned the other recipients should be emailed as such so that they are aware someone else is handling. Instead I am left with a inbox of NOC alerts that have to click through to determine if they are resolved, closed, or otherwise being dealt with by somebody else

Please allow only HTTPS connections to the PI Diagnostics UI web pages, similar to the PI Connector administration pages. Not only is this more secure, but it would also open up the possibility of using the PI Diagnostics UI on a remote computer.

If you install PI Diagnostics 2.5.4.0 when you have PI Diagnostics 2.5.2.0 already installed, PI Diagnostics x64 Prerequisites 2.5.4.0 and PI Diagnostics x86 Prerequisites 2.5.4.0 will not replace their existing 2.5.0.0 counterparts. Instead, the 2.5.0.0 counterparts are left as-is. Please change the PI Diagnostics install kit to replace the 2.5.0.0 versions of PI Diagnostics Prerequisites with the 2.5.4.0 versions.

Customer does not want to see that "All machines for your PI System" 219876543 down, if system 219876543 only consists of one PI Server. Customer would like if we could refine our System alerts if PI Agent is only down for a single machine.

For remote assets, transferring the entire log files could be taxing on the network. Limit the transfer to aspects of the log that are essential for troubleshooting.

Customer would like health tags to monitor PI Agent and PI Diagnostics Services in order to monitor and record their activity.

I'd like to customize the email alerts for my PI system so that alerts that appear do not show the site - as I don't want to mislead alert contacts as to where the issue exists.

I'd like help with being notified when my data is stale and help determining why it's stale.

Add capability to mPI to detect that services are no longer responsive or in a bad state - e.g. when an AF collective is out of sync and the service becomes not responsive, this is not detected by mPI and not flagged by the NOC

I'd like to be able to define a "line" related services that are monitored in the NOC, and then permit that line to be put into maintenance using a physical button or switch (something that is proximate to the line, and does not require computer interaction).

I'd like to be able to show my management an estimate of how much value the NOC delivers in dollars or FTE saved, so I can justify NOC coverage when renewing NOC services.

When you open the Services program (services.msc), the PI Diagnostics Service and the PI Diagnostics UI Service both do not have a description. Please provide one.

I'd like the infrastructure that supports NOC services to be FIPS compliant.