Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ PI Server Installation and Configuration (PI Server 2018)

Learn about performance counters

  • Last UpdatedFeb 12, 2025
  • 2 minute read

PI Notifications Service creates performance counters for each notification rule. You can use these counters for troubleshooting. It has performance counters for monitoring the status of notification rules.

The following counters are provided:

  • Escalations in Progress

    Number of active escalation teams in progress.

  • Escalations Scheduled

    Number of escalation events scheduled since the start of PI Notifications Service.

  • Event Frame Changes Observed

    Number of event frame changes received from the AF server since the start of PI Notifications Service. Changes received cause notification instances to start, end, and change state.

  • Failed Sends

    Number of failed send attempts since the start of PI Notifications Service.

  • Failed Sends / sec

    Rate of failed send attempts per second. This counter displays the difference between the values observed in the last two samples divided by the duration of the sample interval. This counter is not an average over time.

  • History Updates

    Number of history updates written since the start of PI Notifications Service. History updates include state changes, sends, resends, and escalations events.

  • Last Update Change to Process Time

    The number of milliseconds the last online change item took to process since the time the change was made in the PI AF server. This counter is updated every time the service completes processing an item.

  • Last Update Receipt to Process Time

    The number of milliseconds the last online change item took to process in PI Notifications Service from its receipt time. This counter is updated every time the service completes processing an item.

  • Notification Rules in Error

    Number of notification rules in error in PI Notifications Service.

  • Running Notification Rules

    Number of running notification rules in PI Notifications Service.

  • Sends in Progress

    Number of send attempts currently in progress.

  • State Changes Observed

    Number of notification state changes recorded since the start of PI Notifications Service. This includes state changes that may not have caused sends because the notification went into a lower state or was within the non-repetition interval.

  • Stopped Notification Rules

    Number of stopped notification rules in PI Notifications Service.

  • Successful Sends

    Number of successful send attempts since the start of PI Notifications Service.

  • Successful Sends / sec

    Rate of successful message sends per second. This counter displays the difference between the values observed in the last two samples divided by the duration of the sample interval. This counter is not an average over time.

  • Total Sends

    Number of attempts to send messages to subscribers since the start of PI Notifications Service.

  • Total Sends / sec

    Rate of attempts to send messages to subscribers per second. This counter displays the difference between the values observed in the last two samples divided by the duration of the sample interval. This counter is not an average over time.

  • Total Updates Processed

    The number of total changes received from the PI AF server since the start of PI Notifications Service. This is the number of changes PI Notifications Service has processed from AFSDK's FindChangedItems calls.

  • Total Updates Processed / sec

    Rate of total changes processed from the PI AF server. This counter displays the difference between the values observed in the last two samples divided by the duration of the sample interval. This counter is not an average over time.

TitleResults for “How to create a CRG?”Also Available in