AdminJanelle Minich (Product Manager, OSIsoft)

My feedback

  1. 5 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Manageability » Health  ·  Flag idea as inappropriate…  ·  Admin →
    AdminJanelle Minich (Product Manager, OSIsoft) commented  · 

    Hi Nebojsa Krstic,

    While I agree with @Steve Kwan that we should try to get to the root of why your buffers are becoming corrupt, I also think it would be helpful to provide a health incident if that happens. I'll do some research on my end to learn how we might be able to surface that.

    How often are your queues becoming corrupt? Have you been able to figure out what might be causing this (perhaps a power outage? or bad sector on a disk or something?) I would like to know more about how frequently this happens for you, and what might be causing it.

    thanks,
    Janelle

    AdminJanelle Minich (Product Manager, OSIsoft) commented  · 

    Hi Nebojsa,

    a couple of comments on your last response:
    PI System Health will monitor the health of the PI Data Archive in a few ways - we will use some windows performance counters, and we will also be able to talk to the Data Archive directly and query any health incidents that it is able to publish. As time goes on and we release new versions, I expect the Data Archive to add to the list of incident types that it detects and reports to PI System Health.

    As to the comment about ports, unfortunately, that is not something I can change. The software will need to communicate on a port. It can't use a port that's already in use, such as 5450. There are several pieces of software that are required to enable PI System Health. PI Web API is one - the good news is, that port is configurable, so you can set that yourself. We will also rely on a Connector, which uses Relay technology. There is a specific port needed for that, from the relay to the Data Archive and to AF - I believe they are using 5672, but you can double check the documentation.

    All of the port requirements will be clearly documented and communicated when we have our first release, at the end of 2017. Thank you so much for your interest!

  2. 9 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Manageability » PI System Health  ·  Flag idea as inappropriate…  ·  Admin →

    OSIsoft is committed to providing customers with a more manageable system. We are working hard to solve the problems of deployment, security, and standardized health messaging within our products.

    PI System Health and PI System Directory were early steps in the manageability story, and we learned a lot thanks to significant customer testing and feedback. We also discovered that there is much more to making a truly manageable system through these engagements.  In order to pursue these larger needs surrounding manageability, we will not be releasing PI System Health, and we are putting PI System Directory on maintenance so that our engineering resources can be allocated toward these bigger efforts. As such, there are no additional enhancements for PI System Directory planned at this time.

    As a result, the status of this suggestion will be changed back to “No status” for the time being. Future status updates will be communicated here.

    AdminJanelle Minich (Product Manager, OSIsoft) supported this idea  · 
    AdminJanelle Minich (Product Manager, OSIsoft) shared this idea  · 
  3. 45 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Manageability » Health  ·  Flag idea as inappropriate…  ·  Admin →

    OSIsoft is committed to providing customers with a more manageable system. We are working hard to solve the problems of deployment, security, and standardized health messaging within our products.

    PI System Health and PI System Directory were early steps in the manageability story, and we learned a lot thanks to significant customer testing and feedback. We also discovered that there is much more to making a truly manageable system through these engagements.  In order to pursue these larger needs surrounding manageability, we will not be releasing PI System Health, and we are putting PI System Directory on maintenance so that our engineering resources can be allocated toward these bigger efforts. As such, there are no additional enhancements for PI System Directory planned at this time.

    As a result, the status of this suggestion will be changed back to “No status” for the time being. Future status updates will be communicated here.

    AdminJanelle Minich (Product Manager, OSIsoft) commented  · 

    Jon - we are looking at a way to enable the use case you describe - allowing users to modify AF without having to use PSE or PI Builder.

    Tom LeBay is leading that work, he should be able to provide you with an update, and would probably enjoy hearing more about your use case.

    This will fit into the larger Manageability Portal that we are just starting to work on, of which PI System Health will be a part.

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED