PI Cloud Connect
Welcome to the
PI
Cloud Connect
feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI Cloud Connect. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.
Please note that your ideas and comments posted here are visible to all other users.
- For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal (https://my.osisoft.com) instead of sharing them on this site.
- For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
-
Mark Edited/Deleted PI Cloud Connect Tags on Subscriber
As a PI Cloud Connect subscriber, I would like for PI tags that have been edited or deleted on the publisher end to be marked (renamed or otherwise) on my PI Server, so that I can tell when tags are no longer needed. This way, I can also determine if a tag is not updating because it has been edited/deleted, OR if the tag isn't updating because of a different issue.
3 votes -
Identify a subscription's name from its GUID
- When PI Cloud Connect (from subscriber end) create PI tags on a destination PI server, the exDesc of those tags show the GUID of the subscription that owns it. But there's no built-in way to identity the subscription's name based on the GUID.
It seems reasonable to expect to find a subscription and their GUID in the PI Cloud Connect admin website ➔ Subscriptions ➔ details.
– But it's not there, or anywhere else.In the event that one needs to fix an issue that involves a subscription's GUID, it is important to be able to easily identity the subscription…
2 votes -
PICC Admin Portal Log Availability
It would be useful for the PI Cloud Connect (PICC) portal to include logs related to user activity on the portal such as subscriptions, users, or publications added or removed. The current logs are local and service specific. An enhancement of PICC logging on the portal would be very helpful.
2 votes -
Add support for TLS 1.3 on picloudservices.com
This will make the website faster and more secure.
2 votes -
Add support for HTTP/2 on picloudservices.com
HTTP/2 will make the website load faster. OSIsoft's other websites use it.
HTTP/2 check:
https://http2.pro/check?url=https%3A//www.picloudservices.com/2 votes -
Improve PI Cloud Connect's Security Headers score
PI Cloud Connect currently scores an A from Security Headers. However, this can be improved to an A+ by addressing the issues in the link below.
https://securityheaders.com/?q=www.picloudservices.com&followRedirects=on2 votes -
Limit IP ranges on nodes
As a PI Cloud Connect user, I would like to screen receiving Vendors via their account, but by also by limiting connections to a specific IP or IP range for connections.
2 votes -
Allow entering proxy settings manually
PI Connect should auto-resolve the proxy settings, but then allow the administrator to either set them manually or update them.
2 votes -
Rename Subscriber tags when Publisher tagname changes if a flag is on
When a tag on the publisher side is renamed, the tagname on the subscriber side does not get changed to the new name.
As a subscriber, I would like to have an option when setting up the subscription, to flag the subscription so that if a tag within it is renamed, I can select the flag and the tag names on the subscriber would also be changed ( AF, SMT etc).1 vote -
Options for Detail Error logging
I would like to see increased level of logging to identify potential issues with the operation of PICC especially since the alarms page is deprecated.
1 vote -
Data Transfer status & validation option
As a customer I want an easy way to validate that all the data from publisher side went to the subscriber side, so I know if there are any issues.
1 vote -
Submit picloudservices.com for HSTS preloading
To help ensure that no insecure HTTP requests are attempted against picloudservices.com, please consider submitting it for HSTS preloading.
https://hstspreload.org/?domain=picloudservices.comBefore that can happen, some redirects must be set up. http://picloudservices.com should redirect to https://picloudservices.com, and https://picloudservices.com should redirect to https://www.picloudservices.com.
Since picloudservices.com is used for a much narrower purpose than osisoft.com, the barrier to submission for HSTS preloading should be much lower.
1 vote
- Don't see your idea?