Page Comparison

Data Description

The pi_messages event is used in SAP to monitor PI/PO messages used for SAP integration scenarios.

...

1. If using PowerConnect Java 7.3.0 or Higher
   Set the "lag" in the PO Message extractor to match the PO message timeout duration (e.g. 15 minutes). This delay ensures that by the time PowerConnect Java collects the data, messages will have completed their status transitions (e.g., waiting → systemError or success).
   

   

2. Using Advanced Filters with the Exclude Feature
   Track messages in the waiting status and retain only those that ultimately fail. This method allows you to see messages that were in retry and subsequently encountered an error:
   
   <PIFilters>
<PIFilter>
<status>waiting</status>
<payload>false</payload>
<logs>false</logs>
<excludes>
<status>success</status>
</excludes>
</PIFilter>
</PIFilters>
   
   In the above filter messages with a status of waiting will be collected, stored in the inflight cache and tracked.
   When the final status is set any messages that were successful will be removed by the exclude filter.
   Notice we do not use the onlyfaultymessages filter here because this would not match the messages in waiting status.

Configuration

...

This section of the PI Message Monitor configuration deals with general configuration settings which apply globally.

...

Name	Description	Restart of PowerConnect Required?	Default
Max number of messages per interval	Sets the limit on the number of messages the PI Monitoring plugin will collect per run per filter (per SAP instance) if you have 2 instances, and this is set to the default (100) then the agent will collect 100 messages per instance equal to 200 messages maximum across the entire instance.	No	100
Interval (ms)	How frequently the message collection runs	Yes	60000
Max payload size (KB)	Max size of the payload to collect, this avoids collecting huge payloads that may causes performance issues in the SAP system or target analytics platform	No	10240
In-flight message cache size	Sets the limit on the number of in-flight PI messages the PI Monitoring plugin will track	Yes	1000
In-flight message cache expiry (hours)	Defines how long in hours the in-flight PI messages will be kept in the cache before being removed	Yes	24
PO Message Connection Type	Determine the method (WS or EJB) used to collect PO messages. Do not change without consulting support.	No	WS

Splunk Event

The event will look different depending on the configuration options specified, but here is an example in Splunk:

...