• State Not Answered
  • Replies 1 reply
  • Subscribers 47985 subscribers
  • Views 157 views
  • Users 0 members are here
Options
Related

OPC-UA writes casuing massive events table

Lakshay Mundeja

Regarding a UOC project, we’ve developed a custom service that connects to SNMP-enabled devices (specifically power strips used in data centers) to fetch metrics such as voltage, amperage, etc. The service processes and cleans this data, then writes it directly to instances in Galaxy using the OPC-UA protocol, as Galaxy has been configured as an OPC-UA server.
The workflow is functioning as expected, and we’re successfully receiving all required data. However, we’ve noticed that each write operation results in an entry in the Events table with a description indicating a user.write. Since all updates from OPC-UA are being treated as user writes, this could lead to rapid growth of the events storage — especially considering we have around 18,000 such instances.

Could you please advise:

Is there a way to disable Historian from recording these user.write events specifically for updates coming via OPC-UA?
Alternatively, would it be safe to periodically delete these records via a scheduled SQL job without needing to shut down the Historian?

Parents
  • 0

    Hi  ,

    If you are using High-speed history blocks for Alarms & Events Storage, it is not possible to use SQL scripts via a scheduled SQL job to remove those user write events as they are not in relational tables. In addition, System Platform's galaxy and historian are tied up closely in this context. Any user action, such as OPC UA write, will be treated as event that will be sent to Historian's event log for processing. Here are the options you could use to limit these events.

    1. Use Historian Purge / Archive Utility to purge events manually. You should reach out AVEVA Technical Support to obtain a copy
    2. Reduce the duration of events storage. The default is 168 hours (7 days). See Space management for event and summary history for details
    3. Disable User Events. In System Platform IDE, go to Configure / Galaxy / Alarms and Events and locate Events section. Uncheck “User events” category if audit of user.write is not required. This prevents future user write events from being historized into blocks.

    You should choose one that is the best to your situation. I would recommend Option 2 that will keep user events and purge the old events automatically.

    Hope that the information here would be helpful.

    Regards,

    Jacky

Reply
  • 0

    Hi  ,

    If you are using High-speed history blocks for Alarms & Events Storage, it is not possible to use SQL scripts via a scheduled SQL job to remove those user write events as they are not in relational tables. In addition, System Platform's galaxy and historian are tied up closely in this context. Any user action, such as OPC UA write, will be treated as event that will be sent to Historian's event log for processing. Here are the options you could use to limit these events.

    1. Use Historian Purge / Archive Utility to purge events manually. You should reach out AVEVA Technical Support to obtain a copy
    2. Reduce the duration of events storage. The default is 168 hours (7 days). See Space management for event and summary history for details
    3. Disable User Events. In System Platform IDE, go to Configure / Galaxy / Alarms and Events and locate Events section. Uncheck “User events” category if audit of user.write is not required. This prevents future user write events from being historized into blocks.

    You should choose one that is the best to your situation. I would recommend Option 2 that will keep user events and purge the old events automatically.

    Hope that the information here would be helpful.

    Regards,

    Jacky

Children
No Data