Data Growth and Data Archiving Monitors

There is no specific monitor for data growth. However, if you have set the log level in an agent instance to Information or Verbose, you should limit the log size by adapting the log settings in the Windows Event Viewer. If you want to archive your logs, you can use the export functionality from within the log view.

The notification message queues are another possibility for data growth when using notifications. If the notifications are not processed by their destination system with good performance, the message queues will grow. Notification messages are stored in MSMQ queues or in the local file system. If you choose the notification message storage method No Storage on the Notification Processing tab of the agent instance, notification messages are not stored at all. In this case, notification messages will be lost when an agent instance stops.

MSMQ (Microsoft Message Queuing) is a feature provided by the Windows operating system. If you choose the notification message storage method Microsoft Message Queuing (MSMQ), you can check the message queues on the Computer Management screen of Windows under Start of the navigation pathServices and Application  Next navigation step  Services and Application Next navigation step Message Queuing Next navigation step Private QueuesEnd of the navigation path. Here you find up to four queues for every agent. The queues are named pco_[agent ID]_m, pco_[agent ID]_r, pco_[agent ID]_f, or pco_[agent ID]_e, or pco_[agent ID]_b.

If you choose the notification message storage method File System, notification messages are stored in<PROGRAMDATA>\Queues. This folder contains subfolders for every agent instance named after the agent instance ID.

There are four ways of reducing the size of the message queues:

  • You can control the maximum number of queue items by adapting the corresponding setting on the Notification Processing tab of the agent instance. For more information about this setting, see application help Notification Message Queue and Dispatch Settings.

  • You can deselect the option Keep Expired Messages in the notification message queue and dispatch settings (on the Notifcation Processing tab). With this option selected, notification messages that have expired are moved to the message queue Expired Messages. However, notification messages in the Expired Messages queue are not deleted automatically, so that the queue can grow infinitely. If you deselect the option Keep Expired Messages, notification messages are deleted automatically after they have expired.

  • If you can afford to lose the data stored in those notifications, you can simply delete the message queues on the Computer Management screen of Windows (storage method Microsoft Message Queuing (MSMQ)), or you delete the folder related to your agent instance inside the folder <PROGRAMDATA>\Queues (when using storage method File System). New message queues will be created when you restart the agent instance.

  • If you cannot afford to lose the data, you can do the following:

    • Reduce the rate of notification creation.

    • Increase the performance of notification processing on the destination side. For more information, see the Plant Connectivity Performance and Sizing Guide (under https://help.sap.com/viewer/p/SAP_PLANT_CONNECTIVITY).