Add auditing or a view of statistics for the calls or requests done by each individual application. Allow a PI Admin to see which user or application is making a specific call and see how long it takes to complete to monitor performance and potentially resource intensive Web API calls.

It would be great if as an addition to conventional documentation there was a SWAGGER page with short explanation of methods and parameters (including return types, etc.)

OMF 1.2 specification includes an enhancement to allow the use of propertyoverrides keyword in container messages.
Request is to add this functionality to Web API OMF endpoint specifically for the uom property

For example:
1. device configured with uom, OMF application creates a type specifying that uom.
2 new version of the device changes the uom. OMF application needs to create containers with the new uom, retaining other properties of the type.

The PI Web API exposes a "CanBeAcknowledged" property when reading Event Frames. However, this property is read-only: it cannot be supplied when creating a new Event Frame or updating an existing Event Frame. I would like the ability to include this parameter when creating an Event Frame.

I would like to be able to setup the PI Web API OMF endpoint to point to multiple PI Systems, so that way it is easy to send from this single instance to different production systems or to our development and production environments concurrently

Support Type updates on PI Web API OMF ingress

In the https://pivision-us.oxy.com/piwebapi/admin/search/database.html page the Rebuild Index button does not work. It should allow the pi vision administrator to immediate re-indexing of individual AF database at the time without affecting the usability of the others.

PI Web API 2019 now hides personally identifiable information (PII) in log files. As a PI Web API Administrator, I would like to be able to configure PI Web API to show personally identifiable information in log files, so that it is easier for me to troubleshoot Bearer Authentication issues.

Streamsets controller should have a mirror with http POST calls. It's easier to send data in the body using strongly typed model. (As an example, what if you need to get snapshot values of 1000 pi points). Consider to use POST as a GET in some places where amount of arguments in the url can become an issue.

Currently, it is possible to get the status (Enabled, Disabled) of the analysis via the Analysis controller. However, there is no way to know if the analysis is in error or not. It may be Enabled but not outputting any values due to the errors which are not available in PI Web API.

I would like to use TLS 1.3 to secure communication for PI Web API since is the latest and most secure transport layer cryptographic protocol.

Using PI Web API Admin Utility to use a 3rd party certificate, with no access to recovation servers, the Admin Utility will not able to locate this certificate.

Requesting feature for PI Web API Admin Utility to bypass the certificate checks where the certificate cannot be validated

Similar request:
1. Bypass Certificate Prechecks for PI Integrator Upgrade
2. Allow installer to (optionally) bypass Certificate checks, this feature is only completed for Vision but Vision 2020 do not use PI Web API anymore

Currently if a PI Web API user attempts an action which is not allowed, the error handling is somewhat generic.
Stream and Stream Set controller calls might contain an additional information in the response fields, but not always.
e.g. Trying to create a tag using an existing Tag name results in: 409 with error message “An exception has occurred. Please contact your PI Web API administrator for help in enabling debug mode”
Better response codes would allow developers to add custom application logic and inform end users what went wrong in their request.

As a PI Web API client, I would like bearer authentication to be more performant. So that I can write secure, responsive client applications

BearerAuthenticationProvider should cache WindowsIdentity. Currently ClaimsPrincipal is cached and WindowsIdentity is retrieved for each request from C2WTS.

Adding another action in the StreamSets Controller to Register for StreamSet updates in the form POST streamsets/{WebId}/updates with WebId referring a parent object like an Element or EventFrame would be really helpful to get updates for all attributes that belong to an element, similar to Channel controller behavior.

As a PI Web API Indexed Search Crawler Administrator, I would like there to be more pre-defined scan intervals available in the piwebapi/admin/search/settings.html page to lower the granularity of the jumps between scan intervals available.

The blog post linked below urges customers to disable TLS 1.0 and TLS 1.1 but also mentions that PI Web API supports them.
https://pisquare.osisoft.com/s/Blog-Detail/a8r1I000000GvqGQAS/tls-best-practices-for-pi-web-api

Please drop support for TLS 1.0 and TLS 1.1 from PI Web API to force customers to use a secure configuration.